- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 17:50:20 +0000
- To: public-houdini-archive@w3.org
The CSS Working Group just discussed `make P&V API descriptors optional`, and agreed to the following: * `RESOLVED: keep all fields in @property required` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: make P&V API descriptors optional<br> <TabAtkins> github: https://github.com/w3c/css-houdini-drafts/issues/994<br> <fremy> AmeliaBR: with the at-property rule shipping, people started taking a look<br> <fremy> AmeliaBR: there were complaints that all the fields have to be explicit<br> <fremy> AmeliaBR: and this is not very css-y<br> <fremy> AmeliaBR: in general, css does handle defaults better<br> <fremy> AmeliaBR: and by making all these things be required, you remove some behaviors<br> <fremy> AmeliaBR: reasons why people use this<br> <fremy> AmeliaBR: - transition values<br> <fremy> AmeliaBR: - prevent inheritance<br> <fremy> AmeliaBR: - provide default value<br> <fremy> AmeliaBR: you don't always want all three<br> <fremy> AmeliaBR: and now you have to set all of them, which is not always useful<br> <fremy> AmeliaBR: worse, you cannot say "this is a color or it is invalid"<br> <fremy> TabAtkins: that default value thing is a different issue<br> <fremy> TabAtkins: I agree we should fix this<br> <fremy> TabAtkins: the other two cases<br> <fremy> TabAtkins: the inheritance one is that in JS, true has a default value is not logical<br> <fremy> TabAtkins: and we don't want to default to inheritance, because this is more costly<br> <fremy> TabAtkins: but having the default be the revert of the normal choice is confusing<br> <fremy> TabAtkins: so, we think forcing people to think about this is good<br> <fremy> TabAtkins: I think that issue is well settled, we really want to keep this in<br> <fremy> TabAtkins: for the syntax, we could use the unrestricted syntax "*" as a default<br> <fremy> TabAtkins: but I don't think that this is what you want<br> <fremy> TabAtkins: because it cannot do anything useful for you with this syntax<br> <fremy> TabAtkins: if we make this required, authors get an error, and they learn about this<br> <fremy> TabAtkins: and they realize they could have a better behavior<br> <AmeliaBR> q?<br> <fremy> TabAtkins: and "*" is not that common so I don't think it will be common enough to warrant the default<br> <fremy> TabAtkins: and there are other places in css where we force people to specify a value even if we have an obvious default<br> <fremy> TabAtkins: like for example fonts<br> <fremy> TabAtkins: we force you to say "serif" as fallback<br> <fremy> TabAtkins: even though it could be implied<br> <fremy> TabAtkins: but we thought forcing people to think about the fallback is useful<br> <fremy> AmeliaBR: you said that throwing an error makes more sense<br> <fremy> AmeliaBR: but in the non-declarative syntax, this works differently<br> <fremy> emilio: there are browsers where you can see CSS errors<br> <fremy> emilio: ;-)<br> <fremy> TabAtkins: I think this information is surfacable<br> <fremy> TabAtkins: if some browsers have a less-than-useful way of surfacing this, we can fix<br> <fremy> TabAtkins: but I still think "hey this doesn't work" is better than making it work less well<br> <fremy> TabAtkins: AmeliaBR do you feel about this strongly?<br> <fremy> AmeliaBR: not a huge deal I guess, won't object<br> <fremy> AmeliaBR: however, I think that the solution to the other issue is very important<br> <fremy> TabAtkins: yes, that's another issue, and there is another thread about that, and I think we are in agreement with what you wanted?<br> <fremy> AmeliaBR: can you send a pointer?<br> <fremy> TabAtkins: yes, issue ???<br> <astearns> https://github.com/w3c/csswg-drafts/issues/5370<br> <fremy> TabAtkins: so, it sounds like we should be able to resolve to close this issue no change for now<br> <fremy> TabAtkins: any final objection?<br> <fremy> RESOLVED: keep all fields in @property required<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/994#issuecomment-667252362 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 July 2020 17:50:22 UTC