- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 May 2018 10:34:37 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts: == [cssom] Consider removing setPropertyValue / setPropertyPriority. == They haven't been implemented anywhere even though they're in the spec since forever, and I'm trying to get every UA to do the spec'd thing in setProperty and finally be interoperable here. They'd also do the wrong thing with logical properties, etc. So it would be nice if, lacking a good use-case for this and implementation interest, this was removed from the spec. This is conceptually something that could be done, however we'd end up with a bit of pain trying to define how it should interact with mutation observers and such, which is something that no UA has implemented interoperably in setProperty until lately. @zcorpan @dbaron wdyt? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2680 using your GitHub account
Received on Tuesday, 15 May 2018 10:34:39 UTC