- From: Øyvind Stenhaug <oyvinds@opera.com>
- Date: Wed, 10 Oct 2012 13:35:45 +0200
- To: "Simon Fraser" <smfr@me.com>
- Cc: "Yves Lafon" <ylafon@w3.org>, www-style@w3.org
On Tue, 09 Oct 2012 17:58:57 +0200, Simon Fraser <smfr@me.com> wrote:
> On Oct 9, 2012, at 7:36 am, Øyvind Stenhaug <oyvinds@opera.com> wrote:
>>
>>
>> * Chrome drops the entire @keyframes rule (but things like "foo{}" or
>> "body{background:red}" just become regular stand-alone declaration
>> blocks(!))
>
> Same happens in Safari; that was recently fixed. Try a canary/nightly
> build.
Ah, OK, thanks. Looks like Chrome canary still drops the entire @keyframes
rule if it doesn't find anything matching (future CSS 2.1 / Values Level
3-style) PERCENTAGE while looking for a keyframe selector. It doesn't move
stuff outside the @keyframes as stand-alone declaration blocks, and it now
keeps keyframes with selectors like "-20%" and "200%" around in the OM.
The implementations are still divergent, though.
--
Øyvind Stenhaug
Core Norway, Opera Software ASA
Received on Wednesday, 10 October 2012 11:36:22 UTC