Contact emails
fla...@chromium.org, vol...@chromium.org
Spec
http://www.w3.org/TR/css3-positioning/
Summary
position: sticky is a new way to position elements and is conceptually similar to position: fixed. The difference is that a stickily positioned element behaves like position: relative within its parent, and only sticks to the viewport as far as its parent container allows.
Link to “Intent to Implement” blink-dev discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Interoperability and Compatibility Risk
No interference with pre-exisitng APIs.
Internet explorer: Public support
Firefox: Shipped
Safari: Shipped (prefixed)
Web developers: Positive
OWP launch tracking bug
Entry on the feature dashboard
Summary
position: sticky is a new way to position elements and is conceptually similar to position: fixed. The difference is that a stickily positioned element behaves like position: relative within its parent, and only sticks to the viewport as far as its parent container allows.
Link to “Intent to Implement” blink-dev discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Interoperability and Compatibility Risk
No interference with pre-exisitng APIs.
Internet explorer: Public support
Firefox: Shipped
Safari: Shipped (prefixed)
Yay! Couple questions:On Mon, Oct 31, 2016 at 10:54 AM, Robert Flack <fla...@chromium.org> wrote:Probably want to use this link:Summary
position: sticky is a new way to position elements and is conceptually similar to position: fixed. The difference is that a stickily positioned element behaves like position: relative within its parent, and only sticks to the viewport as far as its parent container allows.
Link to “Intent to Implement” blink-dev discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Interoperability and Compatibility Risk
No interference with pre-exisitng APIs.
Internet explorer: Public support
Priority=medium - that's a positive signalFirefox: Shipped
Safari: Shipped (prefixed)
What's the status of interop testing against these other implementations? Are you aware of any differences in behavior? Have we been sharing tests between the implementations at all?
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Going to recuse myself from this one as I was involved in the implementation.On Mon, Oct 31, 2016 at 2:17 PM, Rick Byers <rby...@chromium.org> wrote:Yay! Couple questions:On Mon, Oct 31, 2016 at 10:54 AM, Robert Flack <fla...@chromium.org> wrote:Probably want to use this link:
Summary
position: sticky is a new way to position elements and is conceptually similar to position: fixed. The difference is that a stickily positioned element behaves like position: relative within its parent, and only sticks to the viewport as far as its parent container allows.
Link to “Intent to Implement” blink-dev discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Interoperability and Compatibility Risk
No interference with pre-exisitng APIs.
Internet explorer: Public support
Priority=medium - that's a positive signalFirefox: Shipped
Safari: Shipped (prefixed)
What's the status of interop testing against these other implementations?
Are you aware of any differences in behavior? Have we been sharing tests between the implementations at all?+1, this was my question as well. The implementation had a number of complicated bits in it that took time to get right. It would be really good to have interop tests upstreamed.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
I have discovered several differences in the Safari and Firefox implementations