- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jan 2022 22:05:52 +0000
- To: public-css-archive@w3.org
While having all elements default to style containers can cause issues for non-inherited properties (like @una's background-color example), I think it works out great for inherited properties: checking the parent font size, or current font-style, weight, color, etc. Those use-cases are very handy for solving style-toggle use cases (if parent is italic, child should be normal, and vice versa). For use-cases where it's important to query a specific container (including user-defined container types like 'containers with backgrounds'), setting a `container-name` makes it much more robust against the possibility of accidental intervening containers. Whether or not we revisit this resolution, I would still push authors towards naming containers when that's important — as it is with `background-color`. I'm happy to revisit this if we want to put it back on the agenda (or discuss it as a part of resolving #6644), but at this point I still think we made a reasonable decision. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6393#issuecomment-1013505085 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 January 2022 22:05:53 UTC