- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jun 2019 16:53:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `percentage opacity`, and agreed to the following: * `RESOLVED: No change to spec` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: percentage opacity<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3342<br> <dael> ericwilligers: The argument is opacity can be % or number. opacity prop says same. Not browser impl that. We're proposing to impl but want to ping other browsers to make sure they're okay with it.<br> <dael> ericwilligers: to allow opacity to accept %<br> <dael> AmeliaBR: Has anyone looked and found reason not to? Or has no one prioritized?<br> <dael> myles: We're happy to adopt. % opacity is good in every context<br> <dael> Rossen_: Other opinions or objections to resolve in favor of %?<br> <dael> ericwilligers: Moz?<br> <dael> emilio: No strong opinion. Reasonable. As long as it doesn't cause a conflict<br> <dael> ericwilligers: Serializes as a number<br> <dael> AmeliaBR: We don't have anywhere we're using opacity and they're ambig. In color it's defined by positio in param list. In all others it's single value. No parsing concern<br> <dael> ericwilligers: Thanks everyone<br> <dael> AmeliaBR: It's resolve no change to spec.<br> <dael> Rossen_: Prop: No change to spec<br> <dael> RESOLVED: No change to spec<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3342#issuecomment-505958044 using your GitHub account
Received on Wednesday, 26 June 2019 16:53:07 UTC