- From: Rubén López via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Mar 2018 11:06:35 +0000
- To: public-css-archive@w3.org
Sure you can use JS+DOM hacks (based on IntersectionObserver) to figure out when something started to stuck. The exact same argument could be given for position:sticky itself. Plenty of websites implement(ed) it with JS+DOM hacks. And yet, browsers decided to support position:sticky natively to make it more convenient, less hacky, and more robust. Does anyone have any better argument against the proposal in this issue than "it can be done with JS+DOM hacks"? Or at least one that is consistent with the decision to implement position:sticky in the first place? -- GitHub Notification of comment by rubenlg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1660#issuecomment-374558424 using your GitHub account
Received on Tuesday, 20 March 2018 11:06:43 UTC