Re: [css3-animations] Where in the cascade do animations go?

On Sat, 26 Nov 2011 00:52:46 +0100, L. David Baron <dbaron@dbaron.org>  
wrote:

> http://dev.w3.org/csswg/css3-animations/#animations says:
>   # This overrides the value specified in the normal styling system.
>
> I'm opposed to allowing animations to override user-!important
> rules.  It's not clear if the above sentence was meant to imply
> that, though.
>
> The question that I'm not sure of is whether they should override
> !important rules in Author and Override style sheets.
>
> In particular, given the following existing CSS cascade concepts, I
> see the following as reasonable choices for where animations should
> fall in the cascade:
>
>   1. UA normal rules
>   2. User normal rules
>   3. Presentational hints
>   4. Author normal rules
>        [option A for animations: insert animations here]
>   5. Override normal rules
>        [option B for animations: insert animations here]
>   6. Author !important rules
>   7. Override !important rules
>        [option C for animations: insert animations here]
>   8. User !important rules
>
> In Gecko I implemented option (C).

It doesn't look like "!important" is disallowed in @keyframes in the  
current draft. The spec should say, I don't know if it makes sense. It's a  
possibility to allow "!important" animation styles and either let it end  
up before[A] or after[B] override style:

1. UA normal rules
2. User normal rules
3. Presentational hints
4. Author normal rules
     [option A - animations normal rules here]
5. Override normal rules
     [option B - animations normal rules here]
6. Author !important rules
     [option A - animations !important rules here]
7. Override !important rules
     [option B - animations !important rules here]
8. User !important rules


 From the spec:

"In the case of multiple animations specifying behavior for the same  
property, the animation defined last will override the previously defined  
animations."

Perhaps "!important" in @keyframes property declarations should be a way  
of overriding that behavior instead?

-- 
Rune Lillesveen
Layout Group Manager
Core Technology Department
Opera Software ASA

Received on Monday, 28 November 2011 10:49:16 UTC