- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 11:33:16 +0000
- To: public-css-archive@w3.org
Precise proposal: ``` position: <position-type> || <position-attachment> || <position-container> <position-type> = static | relative | sticky | absolute | fixed <position-attachment> = auto | local | scroll | viewport <position-container> = nearest | farthest ``` * Temporarily removing the `<dashed-ident>` from "container", as that's a separate issue. We can add it back later. * The `fixed` value causes an unspecified attachment/container to default to `farthest` and `viewport`. Otherwise it's identical to `absolute`. * Other than the above, omitted values default to `absolute`, `nearest`, and `auto`. * The property's initial value is still `static`, of course. ------- Another possible slight variant: ``` position: static | relative | sticky | fixed | [ absolute || <position-attachment> || <position-container> ] (<position-container> and <position-attachment> as defined above) ``` * This disallow silly combinations of static/etc with attachment/container values, and leaves open the possibility of other type-specific controls (I think `sticky` has a chance to grow some more, for example) * `fixed` also loses configurability, which is probably good. `fixed viewport` is redundant; `fixed local` is contradictory. It just "behaves as " `absolute nearest viewport`. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12607#issuecomment-3210146923 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 11:33:17 UTC