- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2022 16:34:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Revisit decision to make style the default container type`, and agreed to the following: * ``RESOLVED: Initial value is `none` `` * `RESOLVED: All elements are style containers by default.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: Revisit decision to make style the default container type<br> <Rossen_> q?<br> <TabAtkins> miriam: There's been more discussion. I left a summary, well, longer than that, at the end fo the thread. No responses since.<br> <TabAtkins> miriam: So same question as last time - last time we talked about it it split into several questions.<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1158184820<br> <TabAtkins> miriam: 1) Do we need style queries? I think we do, I argued for it.<br> <TabAtkins> miriam: 2) If we have them, should every container be a style container by default. I think answer is yes for authors, question is perf.<br> <TabAtkins> miriam: In convo with emilio it seems the perf issues are less (maybe not none) if the impl first matches selectors then looks for containers<br> <chris> rrsagent, draft minutes<br> <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/22-css-minutes.html chris<br> <TabAtkins> miriam: If you're going the other way and matching containers first, and everything's a container, you don't get much filtering.<br> <TabAtkins> miriam: Those perf issues are only for people using broad container queries (not using name, etc) and broad selectors. Multiplying those together means lots of searching<br> <TabAtkins> miriam: I don't know how bad that perf hit would be, so hard for me to judge on that.<br> <TabAtkins> miriam: Proposal moving forward is [whoops, missed]<br> <TabAtkins> miriam: If we start now with an initial value of none, browsers can release size queries, and I think that's the right syntax<br> <TabAtkins> miriam: Other question: people will set contianer types in various places, also names<br> <TabAtkins> miriam: Suggestion was to set type in another longhand. But that doesn't work for names.<br> <TabAtkins> miriam: I think the general solution is an additive cascade. No specific solution, need general solution here.<br> <Rossen_> q?<br> <TabAtkins> Rossen_: Any further comments?<br> <futhark> q+<br> <TabAtkins> futhark: I'm supportive, I said so on her writeup<br> <TabAtkins> futhark: Positive to the proposed resolutions<br> <Rossen_> ack futhark<br> <astearns> read the comment and support the suggested resolution<br> <TabAtkins> futhark: Important thing now for chrome and safari is to end up with th einitial value of `none`, will let us ship CQs without having to worry about this idea<br> <TabAtkins> s/this idea/whether everything's a style container/<br> <TabAtkins> futhark: We're exploring style queries; right now it doesn't sound that bad to have them as default<br> <TabAtkins> fantasai: I'm in favor of miriam's points<br> <TabAtkins> Rossen_: Miriam could you summarize?<br> <TabAtkins> miriam: First resolution, initial value is `none`<br> <chrishtr> +1 to Miriam's proposed resolution.<br> <TabAtkins> Rossen_: Objections?<br> <SebastianZartner> +1 from me, too<br> <TabAtkins> RESOLVED: Initial value is `none`<br> <TabAtkins> miriam: Since style queries are in the spec, probably need a resolution for every element being a style container by default. We'll spec that out and adjust as needed as impls start showing up.<br> <TabAtkins> fantasai: Resolution si that every element *is* a style container, regardless of `container-type`.<br> <TabAtkins> emilio: Still skeptical about this.<br> <TabAtkins> emilio: Gecko's CQs are like Blink's. It's a little more annoying to have every element be a style container.<br> <TabAtkins> fantasai: Argument is a lot of people will do that anyway because it's useful to query, so you'll take that hit on a lot of pages anyway.<br> <TabAtkins> fantasai: That's our expectation.<br> <TabAtkins> emilio: I don't know if my expectation matches, but you know more about CSS authors. Okay with that for now, guess I don't object.<br> <TabAtkins> RESOLVED: All elements are style containers by default.<br> <SebastianZartner> Congrats Miriam!<br> <fantasai> Side question, should 'none' be 'normal' now since everything's a style container?<br> <bramus> Nice!<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1163348533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 June 2022 16:34:06 UTC