Re: [css-houdini-drafts] [css-properties-values-api] inherits should be true by default

The CSS Working Group just discussed `inherits should be true by default (CSS Props and Value)`, and agreed to the following resolutions:

* `RESOLVED: inherits arg is required`
* `RESOLVED: published Properties and Values as WD and announce intent to transition to CR soonish`

<details><summary>The full IRC log of that discussion</summary>
&lt;nainar> Topic: inherits should be true by default (CSS Props and Value)<br>
&lt;nainar> Github: https://github.com/w3c/css-houdini-drafts/issues/434<br>
&lt;fantasai> [that topic line should shift to replace the ...]<br>
&lt;fantasai> TabAtkins: Question is should registered custom properties be inherited by default<br>
&lt;fantasai> TabAtkins: regular custom properties are inherited by default<br>
&lt;fantasai> TabAtkins: Lea and Anne found it confusing that registered ones don't<br>
&lt;fantasai> TabAtkins: The standard for doing option bags is that an unspecified one defaults to something falsy<br>
&lt;fantasai> TabAtkins: i.e. undef is false<br>
&lt;astearns> s/Anne/Ana/<br>
&lt;fantasai> TabAtkins: if you don't define a flag, we treat it as false<br>
&lt;fantasai> TabAtkins: We could swap the boolean<br>
&lt;fantasai> ....<br>
&lt;dbaron> https://w3ctag.github.io/design-principles/#prefer-dict-to-bool<br>
&lt;fantasai> dbaron: ...<br>
&lt;fantasai> [scintillating naming discussions]<br>
&lt;fantasai> [extra sparkly on acount of all the gold and mirrors]<br>
&lt;fantasai> franremy: Maybe it should be required<br>
&lt;dbaron> ?: can we make the parameter in the dictionary required?<br>
&lt;fantasai> TabAtkins: Seems like best option, to make it a required key<br>
&lt;dbaron> franremy: non-inherited is good for performance<br>
&lt;fantasai> iank_: Good idea to make sure author has to decide<br>
&lt;fantasai> SimonSapin: Gecko uses reset for properties that don't inherit<br>
&lt;fantasai> dbaron: That's not web-exposed though<br>
&lt;surma> s/?/iank_/<br>
&lt;fantasai> TabAtkins: I prefer making arg required, so ppl don't default into non-performant option<br>
&lt;fantasai> RESOLVED: inherits arg is required<br>
&lt;fantasai> [actually that Topic: ... line should be Properties and Values]<br>
&lt;fantasai> iank_: we have just a few more things to fix before shipping<br>
&lt;fantasai> fantasai: So, you're like "we got a few bugs and then we're going to ship it"<br>
&lt;fantasai> fantasai: What's the state of the spec<br>
&lt;fantasai> fantasai: Has it been published recently?<br>
&lt;fantasai> ...<br>
&lt;fantasai> fantasai: If it hasn't been published recently but is reasonably stable, then let's publish ASAP, sendout Last call for Comments announcements, and prep for CR.<br>
&lt;fantasai> fantasai: Any reason not to do that?<br>
&lt;fantasai> RESOLVED: published Properties and Values as WD and announce intent to transition to CR soonish<br>
&lt;fantasai> fantasai: If implementations are getting ready to ship something, and the spec is not in CR, then we should be putting the spec in CR<br>
&lt;fantasai> fantasai: Because the process for doing so triggers review from people who aren't paying attention because last they heard was it was an exploratory early-stage working draft<br>
&lt;SimonSapin> fantasai +1<br>
&lt;fantasai> fantasai: It's better to solicit people's comments before shipping, so we should make an effort to publish and announce the intent to transition before we ship things<br>
&lt;fantasai> (fantasai: Sometimes it's not possible to make the transition, e.g. for Transitons /Transforms / Animations, there's a chunk of work blocking CR even though implementations have shipped already, but in the general case we should try to get the specs to CR ahead of shipping)<br>
&lt;fantasai> This also signals to other implementations who don't have Google's vast resources to rewrite things multiple times that the spec has stabilized and now is a good time to implement :)<br>
&lt;Rossen> Implementation status: Chrome is shipping the an experimental work in Canary. Mozilla has a developer working on it as well. Microsoft and Apple are under consideration<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/434#issuecomment-319322239 using your GitHub account

Received on Tuesday, 1 August 2017 09:42:23 UTC