[css-cascade] Change the precedence order of cascading origins to match reality better? #1658
Description
Currently, the CSS Cascade spec states that animation declarations shouldn't override 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, 2), so devs may start to believe that this is how it should be (e.g. 3). The Chrome bug about this has been reported in 2015, but still there seems to be no visible intent to fix it. Unfortunately I have no data if the corresponding bugs were reported to 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?