W3C home > Mailing lists > Public > www-style@w3.org > August 2012

RE: [css3-animations][bug-14795] Resolution of keyframe selectors outside [0%-100%]

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 6 Aug 2012 20:53:18 +0000
To: "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>
CC: "www-style@w3.org" <www-style@w3.org>, "Edward O'Connor (eoconnor@apple.com)" <eoconnor@apple.com>, "Simon Fraser (smfr@me.com)" <smfr@me.com>, "Dean Jackson (dino@apple.com)" <dino@apple.com>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178291BE1EE50@TK5EX14MBXC221.redmond.corp.microsoft.com>

[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?

Received on Monday, 6 August 2012 20:53:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:58 GMT