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

[csswg-drafts] [css-cascade] Change the precedence order of cascading origins to match reality better?

From: SelenIT via GitHub <sysbot+gh@w3.org>
Date: Fri, 28 Jul 2017 13:04:31 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-246341625-1501247069-sysbot+gh@w3.org>
SelenIT has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-cascade] Change the precedence order of cascading origins to match reality better? ==
Currently, the CSS Cascade spec states that animation declarations [shouldn't override](https://drafts.csswg.org/css-cascade/#cascade-origin) important author declarations. In fact, they do in all browsers except Firefox. There are some articles that appear to describe this overriding as a standard behavior ([1](https://escss.blogspot.com/2015/04/animaciones-transiciones-contra-important.html), [2](https://paulbakaus.com/2017/07/27/more-important-than-important/)), so devs may start to believe that this is how it should be (e.g. [3](https://twitter.com/iamvdo/status/890862651324104704)). The [Chrome bug](https://bugs.chromium.org/p/chromium/issues/detail?id=552085) about this has been reported in 2015, but still there seems to be no visible intent to fix it. Unfortunately I have no data about Safari and Edge.

Wouldn't it be easier to change the behavior of Firefox than to persuade all other browser vendors to change their behavior according to the current spec? Wouldn't it make sense to change the spec to match the reality of the majority of the browsers?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1658 using your GitHub account
Received on Friday, 28 July 2017 13:04:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 10:12:55 UTC