- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Jun 2022 09:00:15 +0000
- To: public-css-archive@w3.org
Since multiple vendors seem to think it's a little late to get creative here, I propose that we do this:
- `container-type:none` is the initial value, and actually means "none", without implying a style container.
- Authors who prefer style-by-default must then do `* { container-type:style; }`.
- Authors who want to add size-container to something must then remember to do `div { container-type:size style; }` to preserve the style container type. For now.
- Additive cascade improves the situation in the future.
I understand that it's not ideal, but I don't understand why it's necessary to do an emergency hack for this particular case when a) other parts of the CSS has had the same problem all the time (contain, animations, backgrounds, etc), and b) the work-around for the near/medium future is basically "remember to add 'style' to container-type".
Yes, other kinds of containers are vaguely planned, and if that somehow makes the situation unacceptable, then we can focus on doing additive cascade _first_.
--
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1154909591 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 June 2022 09:00:17 UTC