- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 28 Aug 2025 20:12:13 +0000
- To: public-css-archive@w3.org
Talking this over with Ian, we both prefer the second syntax proposal, which scopes the new keywords solely to the `absolute` keyword. This allows future extensions to the other keywords without interfering with the `absolute` ones; it also means we're not forced to make the entire syntax space of the abspos keywords *meaningless* for the others. So just to bring it together in a handy package: ``` position: static | relative | sticky | fixed | [ absolute [ <position-attachment> || <position-container> ]? ] <position-attachment> = auto | local | scroll | viewport <position-container> = nearest | farthest ``` * `viewport` might be a confusing name, since it strongly implies the root viewport to most people, I think. Would it be okay to expose `scrollport` to authors as a keyword? Currently we only use it in the specs, not in the API, but I think it's less confusing. Or we can just switch back to `fixed`, now that the "lone" `fixed` is a different keyword. That is, `absolute fixed nearest` would attach it to the scrollport of the nearest CB, "outside" of the scrollable area. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12607#issuecomment-3234805171 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 August 2025 20:12:14 UTC