Rafael Holt wrote: > Barney wrote: > > I think what Rafael wants is for the object to be fixed compared > to the > viewport, but for its initial position to be determined in relation to > its containing element, which could vary. > > I'm afraid you will need a combination of javascript and CSS for > this, > where javascript works out where the element should be positioned > originally. PPK's blog achieves something similar with the navigation > menus in the side colums, you might find your answers by looking > at his > code: http://www.quirksmode.org/blog/index.html > > > Yes, Barney knows what I mean. I feared I'd have to resort to JS and > PPK's blog is exactly what I had in mind. :)
Ahh, I see. The skip to navigation link in the left column. > However, I still wonder whether anyone thinks position:fixed would be > more useful in this sort of implementation (doesn't move when viewport > is scrolled, but is positioned relative to any containing block, not > just the viewport). Not that I'm trying to change anything, I just > wonder if anyone has come across a situation where this would have > been useful. Nope. But I've never come across a situation where I've needed position: fixed either. Not that I'm against it -- I'm happy to use it if a client requests it -- it's just not a necessary interface thing for me. Users are used to things moving when you scroll, so I've never needed to change that. Perhaps it is something that has been discussed by the W3C though? http://lists.w3.org/Archives/Public/www-style/ Zoe -- Zoe M. Gillenwater Design Services Manager UNC Highway Safety Research Center http://www.hsrc.unc.edu ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- 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/
