richard n wrote: > http://www.richardnicholson.com/testing/menu_with_frames6/editorial.html > > It is NOT THE SAME in IE6 as it is in Firefox. > > I think it's better!
Good :-) > [...] You described one of the "dangers" with 'position: fixed'. Overlapping is unavoidable, and is in fact one of the *features* of 'position: fixed'. Same problem as with real frames. As I have written in the article... <http://www.gunlaug.no/contents/wd_additions_15.html> ...under the title: *use 'position: fixed' with care…* "The viewport-size at the User end is at best an unknown factor, and the available space may be quite small." Thus, the scrollable content may end up behind 'fixed' elements in extreme cases / small browser-windows, and there's no way to make it visible - short of disabling CSS. It's different with 'position: absolute' and a bit of scripting - as seen in IE6, as the element is relating to the body _and_ to the viewport at the same time. Still not as flexible as I'd like, but better than 'position: fixed' in some cases. > Hmmm, I'm assuming that this sort of behaviour can not be created > using pure CSS? (Ideally I'd fix the menu horizontally, but not > vertically). I don't think so. At least I haven't managed to create what I'd call "a flawless solution" - yet. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
