- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Sep 2017 22:00:40 +0000
- To: public-css-archive@w3.org
> 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. Wow, then we live in two entirely different worlds: I both saw and implemented myself in my practice *a lot* of sticky cases where the layout didn't change (or wasn't the most important part). The most common thing in a lot of projects I worked on was just adding a shadow and a solid background to make the sticky part visually distinctive from the content beneath. And anyway, if we'd add just a limited amount of supported properties, then, of course, the design possibilities of that subset would be smaller than what would be possible with all the properties supported. But that does not means in any way that those that can be implemented would be useless. Both developers and designers would find ways to use it in the most efficient way, and if there'd be also proper events for hacking around the layout changes, then more complex cases would be possible too. What I'm saying is that we don't need to have everything at once. I'm sure that most of the developers would be happy with just repaint-only styles available at the start instead of _nothing_. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1660#issuecomment-331570486 using your GitHub account
Received on Friday, 22 September 2017 22:00:35 UTC