- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 11 Mar 2026 16:45:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css3 positioning] support position:sticky inside an overflow:hidden|auto on general parents`, and agreed to the following: * `ACTION: flackr to put example in the spec` * `RESOLVED: position:sticky tracks the nearest scrolling container *per axis*` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> flackr: we decided in another discussion that it's reasonable to create a scroll container that onlys scrolls in one axis, and is clip in the other<br> <TabAtkins> flackr: following this line of thought, we can support... one of the use-cases for postiion-sticky responding to an ancestor scroll container, by saying the position-sticky in each axis looks for the nearest container that scrolls in that axis<br> <TabAtkins> flackr: this is a fairly constrained change, doesn't require new syntax, and supports horiz-scoll tables in vertical-scroll docs<br> <TabAtkins> flackr: we've tested it and it seems to work fine. does what users expect<br> <TabAtkins> flackr: so the proposal is that sticky can use different containers for each axis<br> <TabAtkins> astearns: does this cover the original test-case?<br> <TabAtkins> flackr: the original was relying on the implications of overflow:hidden... there are other APIs that can get that to work, I posted a demo<br> <TabAtkins> flackr: my proposal handles the either novel use-case which wasn't handled previously, which can be sticky-translated in different axises by different scrollers<br> <kizu> q+<br> <astearns> ack kizu<br> <TabAtkins> kizu: this is really nice to have. only concern is interop<br> <TabAtkins> kizu: a sticky element that previously didn't work well could start working and sticking<br> <TabAtkins> kizu: but it would be really nice for this to work<br> <TabAtkins> flackr: we expect that, since to set the container up you have to explicitly set overflow:clip on the off-axis, it'll be rare that existing content gets into this use-case<br> <kizu> Ah, yes, with `clip` is will be for sure safer<br> <TabAtkins> flackr: so I expect it to be safe, but experience will tell<br> <fantasai> TabAtkins: Just need to document this use case in the spec, to make clear that it works<br> <smfr> seems fine<br> <fantasai> ACTION: flackr to put example in the spec<br> <TabAtkins> astearns: proposal is position:sticky tracks the nearest scrolling container *per axis*<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: position:sticky tracks the nearest scrolling container *per axis*<br> <TabAtkins> flackr: this is a long issue, there might be other use-cases but the two I mentioned seem to be the main ones<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/865#issuecomment-4040585511 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 March 2026 16:45:05 UTC