[TYPO3-hci] "New top frame" problems

Wed Sep 27 13:38:17 CEST 2006

Kasper Skårhøj kirjoitti:
> Hi folks,
> 
> As the plan goes, I'm trying to build the initial framework for having a 
> top frame. In "alt_main.php", instead of a frameset, this is what I put:
> 
> <body>
>             <div id="menu">
>                 ... menu stuff here with layers and all...
>             </div>
>             <iframe src="./alt_intro.php" id="content" 
> name="content"></iframe>
> </body>
> 
> (In addition there are styles and some JavaScript to position the items 
> correctly)
> 
> 
> I tested it in these browsers:
> - Firefox (Mac)
> - Opera 9 (Mac)
> - Safari (Mac)
> - MSIE 6 (Win)
> - Konqueror (Linux)
> 
> Generally, it works! Layers from within the <div id="menu"> will overlay 
> the iframe, even on top of scrolls bars in the iframe.
> 
> Exceptions are:
> - Konqueror: Nothing seems to be able to lay on top of the iframe here! 
> Means; Everything in the menu area must stay in the menu area. Is there 
> are way to change that?
> - Firefox: Scrollbars will penetrate the layers dropping down over the 
> iframe. Is there are way to suppress this?

if you would use two-frame solution, hv-menu might work better.
Main level would be in the upper frame and sub-menu in the lower.
If you anyway use frames - IFRAME is frame, it doesn't essential
change the situation to use two frames navi and content.
Using iframe the page itself works as if top-frame and the IFRAME
for content as content frame.
HV menu might work also with iframe, if you give name for the page,
which has the 1. level menu and normal page works as if frame page.
The behavior is very close using one frameset with two frames.
Advance using IFRAME is that shortcut could be in layer and they
would be easy to hide.

Have you thought seriously that drop-down menu has a very bad disadvantage.
It can't keep open the active main and sub-module because the menu must 
always close after using - that is not good usability.

Hover-based tabbed menu can keep open active main and sub-module
with consitent way. There is never situation, where the main and 
sub-module would not syncronize.

Cliking main modules just tell the last click - it doesn't always tell 
which main module is really currently active.
If you click the main module link, it has the same effect than clicking 
sub-module link. Clicking sub-module can't change the layout of main 
module, because the ancestor for main and sub-module is the same.

I still keep two frame system with two-level tabbed menu more usable
as drop-down menus. It can be implemented also using IFRAME.

> Generally, I assume these problems can be solved and if not, this new 
> way of shaping the backend is still just an alternative approach - the 
> old frameset is still equally usable for accessing modules.