W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css-position] Events for stickiness changes

From: François REMY via GitHub <sysbot+gh@w3.org>
Date: Fri, 22 Sep 2017 21:45:23 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-331567944-1506116711-sysbot+gh@w3.org>
Yeah, I agree, @tabatkins, myself and so many others in the csswg really just haven't thought about this nearly enough, and that's why we have not found the obvious solution yet. All this time, the solution was to <a href="https://github.com/w3c/csswg-drafts/issues/1656#issuecomment-318479002">detect the problematic declarations</a> and remove them. If we remove declarations one by one, we would eventually reach a stable layout in only `O(nd²)` relayouts, where `n` is the amount of css declarations in the document, and `d` the amount of elements in the DOM!

All the real-word usages of `:stuck`-like things I have seen in the wild (and Edge just implemented position:sticky so I guess I spent some more time looking at real-world usage than most) do change the layout of descendants of the stuck elements. There is no way we can prove these things wouldn't cause circularity. 

GitHub Notification of comment by FremyCompany
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1660#issuecomment-331567944 using your GitHub account
Received on Friday, 22 September 2017 21:45:14 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:18 UTC