My problem is either a bug - or a problem with needs of a "work around"

This is what i've done:

1. First i do two minipanels = Business / Private - including MENUS: Business / Private - respectively.
NOT: all menu-children are graphich .gif-picture with text changing color on default, hover and active...

2. Then one Minipanel (also with other category-name) including the two holding each menu ( Business / Private ) in the content - HERE I set the Panel Tabs (ON)! I've also set "#tabs-menyer_med_flikar-main-2" in all child menus URL who is placed in TAB-2 = higher than TAB-1 -> TAB-1 will else will be the default on each NEW page loading from TAB-2 child's.

3. One Panel Node Template Variants - viewing actual pages, where the Minipanel in point 2. is mounted together with more stuff. ( By that, all the other stuff will NOT be included as a TAB )

PROBLEM:
When going to panel-TAB no 2, and then klick on a sub-menu (child) the page is jumping down as TAB-2 block was placed below the TAB-1 block in firefox. In Safari the jump is stop near at the upper side of TAB-1 (Different reaction)

I've tried to set the css with an extra tag - meaning that all the child tags block will be put away and not taking any vertical space:

.ui-tabs-panel.ui-widget-content.ui-corner-bottom.ui-tabs-hide li {
	display: none !important; }

NOT: by temporarily setting display:block on TAB-hide block (viewed) , i have checked that this tag is working.

BUT - each time clicking on a child-menu in TAB-2 the site will jump down as TAB-2 block was place below the TAB-1 block

My theori is - when loading a new page: - somewhere in the chain of data there is a css setting: "display: block;" for TAB-1 who will be loaded before the next css-tag setting ".ui-tabs .ui-tabs-hide, .ui-tabs .ui-tabs-hide li { display: none !important;}" and the browser do the "jump down" just o,5 sek before css-tags no 2 (with display; none) is rendered and the page is coming up/be viewed.

ANY suggestion to a solution or a workaround?