Re: [csswg-drafts] [css-position-3] Revisit the scroll position of sticky-positioned boxes (#7930)

The CSS Working Group just discussed `[css-position-3] Revisit the scroll position of sticky-positioned boxes`, and agreed to the following:

* `RESOLVED: Revert the change to how scroll position of sticky positioned boxes are calculated`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> flackr: There's a lot in the issue. Basically many years ago we tried to come up with a scrolling position behavior for sticky poisition elements when they overlap. Solved one use case but breaks another common on. Never launched in any browser<br>
&lt;dael> flackr: Prop is revert that change and explore other ways to handle this use case. For this issue it's just to revert<br>
&lt;dael> smfr: What's the behavior after the revert?<br>
&lt;dael> flackr: Current impl behavior that scrollposition of sticky position element is it's calcuated position<br>
&lt;dael> smfr: Doesn't use it's inflow position; that static position I think it's called<br>
&lt;dael> flackr: Sticky position, I think, yes. No one impl it those and many bugs against experiment<br>
&lt;dael> smfr: What about in fixed, assume it's in view?<br>
&lt;dael> flackr: Correct<br>
&lt;dael> TabAtkins: Sorry I missed ping flackr. This seems reasonable. No option is ideal but current impl behavior seems fine and compact impact is scary. Fine with prop<br>
&lt;dael> flackr: I have follow-up on improving edge cases but that's seperate<br>
&lt;dael> astearns: Concerns on reverting?<br>
&lt;dael> astearns: Prop: Revert the change to how scroll position of sticky positioned boxes are calculated<br>
&lt;dael> RESOLVED: Revert the change to how scroll position of sticky positioned boxes are calculated<br>
&lt;dael> astearns: I'm assuming discussion about other solutions are separate issues?<br>
&lt;dael> flackr: Yes<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7930#issuecomment-1371602790 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 5 January 2023 00:51:01 UTC