W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2019

Re: [csswg-drafts] [css-content] Initial value of quotes should be auto (#4074)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 03 Jul 2019 23:45:53 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-508289873-1562197552-sysbot+gh@w3.org>
The CSS Working Group just discussed `Initial value of quotes should be auto`, and agreed to the following:

* `RESOLVED: Add an 'auto' value`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Initial value of quotes should be auto<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4074<br>
&lt;dael> heycam: Commentor is happy with deciding or not on call<br>
&lt;dael> AmeliaBR: Request is a new value auto to be clear. This is lang sensitive default<br>
&lt;dael> dbaron: I think that's the idea<br>
&lt;dael> dbaron: Idea is that WK and Blink use an initial value that is not something they can serialize that triggers lang dep marks. Would like to do in Gecko, but want to be able to serialize and roundtrip<br>
&lt;dael> AmeliaBR: I think this is something authors would want to use. Might not need to set explicitly if it's sensible default.<br>
&lt;dael> heycam: Can use initial to get this unserializable value<br>
&lt;dael> astearns: Is reason b/c no one wanted to impl auto in past? Reason why we did not do this previously?<br>
&lt;dael> dbaron: I don't know. I do know it used to be the spec acted as though you would write all lang dependant values in css in UA stylesheet. Some have non-speedy selectors and it's better to impl in not-css and more direct data from cldr<br>
&lt;dael> AmeliaBR: IN spec have a depend on UA initial value. Not great because means no interop. Sounds like in some UA depends on more than a single value. Having an auto value and the UAs that have a simple initial value auto can resolve to the initial value<br>
&lt;dael> florian[m]: Auto and initial value for lang reasons is reasonable. Considering spec what the behavior is or is it meant to be impl dependent.<br>
&lt;dael> AmeliaBR: Good question. SHould we define auto needs to be sensible lang based<br>
&lt;dael> dbaron: Could be more precise depending on interop situation. Worth follow-up investigation. Worth coming up with more specific, but no one has that written down right now<br>
&lt;dael> florian[m]: If we define what it is eventually I support auto value<br>
&lt;dael> myles: Having the initial value be auto is a good idea. Should do it<br>
&lt;fantasai> https://html.spec.whatwg.org/multipage/rendering.html#quotes<br>
&lt;dael> astearns: Having rough consensus for auto value that is for now impl dependent but it serializes well<br>
&lt;dael> fantasai: HTML spec, I believet his is out of cldr. Has a definition for quotes. Seems to be all we're asking for is an auto value with this behavior built into it. So UA stylesheet just says auto and have this behavior. So we have a definition. Might want to update the def but not defining from scratch<br>
&lt;dael> AmeliaBR: Sounds good. Simplify UA stylesheet. Integrate into CSS.<br>
&lt;dael> fantasai: None of these selectors are HTML specific<br>
&lt;dael> AmeliaBR: But for default HTML namespace.<br>
&lt;dael> fantasai: We can drop the namespace<br>
&lt;fantasai> s/namespace/@namespace/<br>
&lt;dael> AmeliaBR: Either way making it def in CSS rather than HTML means defined for all CSS applications<br>
&lt;dael> myles: Should allow for other browsers to change cldr rules. Shouldn't say must adhere to exactly what cldr says<br>
&lt;dael> florian: Do you have specific ways or jsut fundamental principle.<br>
&lt;dael> myles: I'm sure we have tweaking. Lots of designers and lang experts that have many different opinions in our company. Don't have specific example off top of head<br>
&lt;florian> s/specific ways/specific ways you want to differ from CLDR/<br>
&lt;dael> astearns: Aside from question of defining exact behavior of auto, does anyone object to adding an auto value?<br>
&lt;dael> RESOLVED: Add an 'auto' value<br>
&lt;dael> astearns: I'm open to figuring out if we can define this. Would be good to have specific proposal, not just pointing to another spec ans saying copy. If someone wants to define auto more closely good to open a new issue with a proposal. Sound okay for everybody?<br>
&lt;dael> heycam: Yeah<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4074#issuecomment-508289873 using your GitHub account
Received on Wednesday, 3 July 2019 23:45:55 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:50 UTC