- From: Kevin Babbitt via GitHub <noreply@w3.org>
- Date: Wed, 13 Aug 2025 17:27:14 +0000
- To: public-css-archive@w3.org
kbabbitt has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-gaps-1] Asymmetric start and end offsets == We have a couple of use cases from author feedback where there's a desire to have asymmetric starts and ends for decoration offsets. Examples: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/996 <img width="1392" height="794" alt="Image" src="https://github.com/user-attachments/assets/0a67c7b4-cacc-49c2-94f8-ca5c9806bf82" /> https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/1100#issuecomment-3096717818 <img width="1133" height="787" alt="Image" src="https://github.com/user-attachments/assets/a9148515-e2e5-47bb-ae96-472e8bf16330" /> This is related, but I think distinct, from https://github.com/w3c/csswg-drafts/issues/12024 which contemplates having the offset behavior at the edges be distinct from the rest of the container. The second case above actually might be better served with something other than a gap decoration, at least as they're defined today. The use case calls for a line segment of a specific length, and we define the endpoints of gap decorations relative to the locations of intersections. But the first case I think makes a good argument for `*-rule-offset` to take two values, or perhaps to turn it into a shorthand of `*-rule-offset-start` and `*-rule-offset-end` to control these values separately. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12603 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 August 2025 17:27:15 UTC