Last modified: 2014-02-12 23:55:37 UTC
We should find a way around this, this would be very useful in many places in the user interface.
Personally from experience this is not worth the hassle. The only way you'll get a true position fixed experience is if you use iScroll or similar library http://cubiq.org/iscroll for these browsers which basically involves reimplementing browser scrolling. We already do 'position fixed' in the reference reveal but the experience is not smooth when you scroll and the notification scrolls with you. It's also very hard to detect which browsers to serve to. Personally I'd say WONTFIX - we should use position fixed when we are 100% sure it is available and fall back to position relative/absolute/something else where it is not. Otherwise the experience will not be smooth (not to mention the nightmare of what happens when the user zooms in or out!) This is an interesting read: http://www.quirksmode.org/blog/archives/2010/12/the_fifth_posit.html
I don't see how this bug is currently actionable so closing as INVALID. Feel free to open a specific bug explaining where position fixed is needed to motivate and drive work on this.
