mail archive www-style.w3.org
(List home) (Recent threads) (197 other W3C lists)
Subscription Options
- RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
- Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe (we seem to have lost it) address with "subscribe" in the subject line.
- Moderate traffic list: up to 30 messages per day
- This list contains about 20,567 messages, beginning Mar 2011
- 27 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no
[bug-14795] Resolution of keyframe selectors outside [0%-100%]
Ad
Looking into this open issue [1], I find that both Firefox (Aurora) and IE10 ignore keyframe selectors that are <0% or >100% and simply run the animation as if they weren't present. WebKit (Chrome 21) seems to ignore the entire animation of any keyframe selector is out of bounds. (I have no build of Opera that supports css3-animations at the moment). I propose we specify the behavior implemented by Firefox and IE; it seems more consistent with author expectations of what would happen to an invalid selector. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?i...
On Fri, Aug 3, 2012 at 3:15 PM, Sylvain Galineau wrote:
> Looking into this open issue [1], I find that both Firefox (Aurora) and IE10
> ignore keyframe selectors that are <0% or >100% and simply run the animation
> as if they weren't present.
>
> WebKit (Chrome 21) seems to ignore the entire animation of any keyframe selector
> is out of bounds.
>
> (I have no build of Opera that supports css3-animations at the moment).
>
> I propose we specify the behavior implemented by Firefox and IE; it seems more
> consistent with author expectations of what would happen to an invalid selector.
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?i...Agreed.
(Though it would have been nice, if this weren't constrained by
existing impls, to have it work similarly to, say, radial gradients
stops positioned less than 0%, where the keyframe is still used to
generate a "virtual" 0% keyframe. But we're past that point now.)
~TJ
[Tab Atkins Jr.:]>
> On Fri, Aug 3, 2012 at 3:15 PM, Sylvain Galineau
> wrote:
> > Looking into this open issue [1], I find that both Firefox (Aurora)
> > and IE10 ignore keyframe selectors that are <0% or >100% and simply
> > run the animation as if they weren't present.
> >
> > WebKit (Chrome 21) seems to ignore the entire animation of any
> > keyframe selector is out of bounds.
> >
> > (I have no build of Opera that supports css3-animations at the moment).
> >
> > I propose we specify the behavior implemented by Firefox and IE; it
> > seems more consistent with author expectations of what would happen to
> an invalid selector.
> >
> > [1] https://www.w3.org/Bugs/Public/show_bug.cgi?i...
>
> Agreed.
>
> (Though it would have been nice, if this weren't constrained by existing
> impls, to have it work similarly to, say, radial gradients stops
> positioned less than 0%, where the keyframe is still used to generate a
> "virtual" 0% keyframe. But we're past that point now.)
>Possibly, though in that case you also have to define what happens to the
-10% keyframe selector when the author did define 0%. I find the current
FF/IE approach to be both simple and reasonable. And yes, this is all
getting much harder to change now.
(12/08/04 6:15), Sylvain Galineau wrote: > Looking into this open issue [1], I find that both Firefox (Aurora) and IE10 > ignore keyframe selectors that are <0% or >100% and simply run the animation > as if they weren't present. > > WebKit (Chrome 21) seems to ignore the entire animation of any keyframe selector > is out of bounds. > > (I have no build of Opera that supports css3-animations at the moment).For your information, Opera Next (Opera 12.50 internal) behaves like Firefox and IE10 here. (tested with data:text/html,<!DOCTYPE html><style>@-o-keyframes test { -10% { top: 0em; } 0% { top: 1em; } 100% {top: 10em;} 110% {top: 20em; } } div { border: red solid; position: absolute; -o-animation: test 1s infinite;}</style><div></div> )> I propose we specify the behavior implemented by Firefox and IE; it seems more > consistent with author expectations of what would happen to an invalid selector.Yeah. Cheers, Kenny
[Kang-Hao (Kenny) Lu:]>
> (12/08/04 6:15), Sylvain Galineau wrote:
> > Looking into this open issue [1], I find that both Firefox (Aurora)
> > and IE10 ignore keyframe selectors that are <0% or >100% and simply
> > run the animation as if they weren't present.
> >
> > WebKit (Chrome 21) seems to ignore the entire animation of any
> > keyframe selector is out of bounds.
> >
> > (I have no build of Opera that supports css3-animations at the moment).
>
> For your information, Opera Next (Opera 12.50 internal) behaves like
> Firefox and IE10 here.
>
> (tested with
>
> data:text/html,<!DOCTYPE html><style>@-o-keyframes test { -10% { top:
> 0em; } 0% { top: 1em; } 100% {top: 10em;} 110% {top: 20em; } } div {
> border: red solid; position: absolute; -o-animation: test 1s
> infinite;}</style><div></div>
> )
>
> > I propose we specify the behavior implemented by Firefox and IE; it
> > seems more consistent with author expectations of what would happen to
> an invalid selector.
>
> Yeah.
>Thank you!
Ted, Simon, Dean and other Apple folk: any comments and/or objections?