- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jun 2022 16:16:35 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `rename container-type: none to normal`, and agreed to the following: * `RESOLVED: Change initial value of 'container-type' to "normal"` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: rename container-type: none to normal<br> <TabAtkins> fantasai: Since we made style containment the default on every element, the initial value of container-type is "none".<br> <TabAtkins> fantasai: WAs wondering if we wanted to name that as "normal", which would possibly let us shut off style containment later if needed<br> <TabAtkins> fantasai: No strong opinion.<br> <fantasai> TabAtkins: I agree that renaming to normal works<br> <TabAtkins> miriam: Agree and also don't ahve strong opinion<br> <TabAtkins> astearns: In the issue antti said they weren't opposed to the change<br> <TabAtkins> astearns: But I think they weren't considering the case where we add names to style containers<br> <fantasai> s/weren't/were/<br> <TabAtkins> astearns: So we could put into the issue that we're okay with considering it?<br> <TabAtkins> smfr: If there's more context, I can ping antti and get his response<br> <TabAtkins> astearns: My take is that it's not that container-type has nothing to do with style containers, it's just that everything is a style container, and the only thing container-type *is* doing for style-only containers is letting you set a named style container.<br> <TabAtkins> astearns: I think antti is thinking we've broken the connection to the property entirely<br> <TabAtkins> astearns: would be good to find out<br> <TabAtkins> astearns: Simon, do you want to ping antti and we resolve next week?<br> <TabAtkins> smfr: Believe he's on vacation so might not get a response by next week<br> <TabAtkins> astearns: Alternately we could resolve now and let them bring up an objection later if it's still there?<br> <TabAtkins> smfr: I think I'd prefer that this issue have enough context that antti can read it and be sure he udnerstands the issue<br> <TabAtkins> smfr: But with that, I think I'm okay with resolving and letting him bring up an issue<br> <TabAtkins> fantasai: The two reasons are: 1) because style is a type of container, saying "none" is disingenuous<br> <TabAtkins> fantasai: 2) we might want a way to turn off style container on an element, and using "none no-style" is somewhat awkward. "normal no-style" is more neutral<br> <TabAtkins> fantasai: We're also not allowed to use container-names of "none" and we should keep that restriction, and also exclude "normal".<br> <TabAtkins> astearns: So proposed resolution is to change container-type's initial value to "normal" ,but still resolve "none" as a future value<br> <TabAtkins> ??: How about 'auto' instead of 'normal'?<br> <TabAtkins> fantasai: Could work, but 'auto' usually implies more magic<br> <astearns> s/??/ntim/<br> <TabAtkins> astearns: I slightly prefer normal over auto, but no great argument either way<br> <TabAtkins> I'm lightly for "normal" for the reason fantasai gave<br> <TabAtkins> ntim: No strong preference, just a thought<br> <TabAtkins> astearns: So any objections to normal?<br> <TabAtkins> RESOLVED: Change initial value of 'container-type' to "normal"<br> <TabAtkins> fantasai: TAb suggested in IRC that we just blanket restrict none/normal/auto in custom idents and I propose we do that.<br> <TabAtkins> astearns: Makes sense, but do we have those allowed in the past that would cause compat issues?<br> <TabAtkins> fantasai: Possible but seems unlikely.<br> <TabAtkins> chrishtr: What does that mean?<br> <fantasai> TabAtkins: A custom-ident can never be keyword 'initial'; all global keywords are restricted.<br> <fantasai> TabAtkins: we'd just add this to the list of keywords<br> <fantasai> chrishtr: Could it break content?<br> <lea> +1<br> <fantasai> TabAtkins: if ppl are currently using those names, yes<br> <fantasai> TabAtkins: but they are very generic, so it seems unlikely<br> <fantasai> TabAtkins: but we can check<br> <fantasai> astearns: We should open a new issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7402#issuecomment-1170195051 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 June 2022 16:16:37 UTC