- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Feb 2023 16:39:31 +0000
- To: public-css-archive@w3.org
Apologies for not being there for the discussion, was OOO when this came up. I just caught up with the notes and +1 to the conclusion: "add a magic initial value". That is the easiest thing for authors to understand and also works well with how `overflow` is currently used with SVG. This could use a stab at implementation. In Blink, we don't know whether an element is replaced or not during the style cascade. It happens when building the layout tree. And Idk if there is any spot in the style cascade which would want the used value for overflow instead of the new magic value. I'm assuming the same pattern will be taken up with `overflow-clip-margin`. Right now its default is `padding-box` but a new magic `auto` value here would result in a used value of `content-box` if it applies to a replaced element. The point about authors wanting to specify a different value based on whether the element is replaced or not is a good catch. The proposal for a pseudo-class would have the same issue as above, we don't know this during the style cascade. I expect it won't be a concern for `overflow` since the style cascade can have the new magic value as the resolved value. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7144#issuecomment-1446663552 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 February 2023 16:39:33 UTC