-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of position: sticky? #17
Comments
It seems like this plugin wouldn't even be necessary anymore in many situations 😛 But in terms of performance it would definitely be handy as I can let the browser do the calculations. Perhaps I can make it so the polyfill can hook into the plugin using a wrapper, but then it would be nice that the current engine is hook-able too because that will save file size. I guess I'm making it a bit too complex that way, but I'm just going out on a limb here :) |
Not sure if we can save filesize that way as position:fixed will need to be supported for several years, of course. Let us know any ideas regarding the implementation or plans on your side to implement it, we will probably tackle this issue soon and try to integrate it in angular-sticky. |
Next week I'm off from work and you triggered me with this request ;) I might also need to rely more on modernizr if I want to support both sticky methods, but we'll see. I'll keep you informed. |
That's good to know! We'll wait for potential progress then, no pressure :) |
@harm-less Any updates so far? |
@harm-less @psaniko There might be a CSS based fix for the flickering of sticky elements on iOS. The combination of forcing hardware acceleration (by using 3D transform) and the usage of backface-visibility did the trick. Applying |
Are there any plans to support the upcoming specification of stickily positioned elements?
https://www.w3.org/TR/css-position-3/#sticky-pos
We realize this is quite early and not at all widely supported but we need smooth stickyness on iOS devices and are considering switching to fixed-sticky because of this. As this switch would come with a lot of drawbacks, we would like to know if such an implementation is on the horizon or even at all possible with the current approach.
The text was updated successfully, but these errors were encountered: