CSS keyframe animations in Shadow DOM

1,059 views
Skip to first unread message

Toby Schachman

unread,
Nov 18, 2013, 6:30:33 PM11/18/13
to polym...@googlegroups.com
Hi,

What's the current best practice to use a CSS keyframe animation on an element within a shadow root?

That is, without Polymer, just Chrome Canary with Experimental Web Platform features on.

Also, there was some talk of new CSS selectors (^^ and ^). Any updates on these? Can they be used? Are there docs/spec? Does this relate to my above question?

Toby

Steve Orvell

unread,
Nov 18, 2013, 6:37:56 PM11/18/13
to Toby Schachman, polym...@googlegroups.com
What's the current best practice to use a CSS keyframe animation on an element within a shadow root?

It should just work: http://jsbin.com/Icewemug/2/edit

Also, there was some talk of new CSS selectors (^^ and ^). Any updates on these? Can they be used? Are there docs/spec? Does this relate to my above question

These are now implemented in Canary!

I think Rob's excellent summary is a good place to start:



Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Toby Schachman

unread,
Nov 18, 2013, 7:19:44 PM11/18/13
to Steve Orvell, polym...@googlegroups.com
Thanks!

I got tripped up because I was doing a transform animation and Canary unprefixes animations but keeps transforms prefixed. So the fix is just to list an exponential combination of prefixes ;)


Also thanks for the link to Rob's summary. Very helpful!

Toby

Eric Bidelman

unread,
Nov 18, 2013, 10:07:33 PM11/18/13
to Toby Schachman, Steve Orvell, polym...@googlegroups.com
Steve, I recall @animation defines did _not_ work inside of <polymer-element> at one point.


Did this change? Should I remove that commentary?

Steve Orvell

unread,
Nov 18, 2013, 10:11:48 PM11/18/13
to Eric Bidelman, Toby Schachman, polym...@googlegroups.com
Yeah, this bug has been fixed.

It was part of addressing this issue, I believe:

Reply all
Reply to author
Forward
0 new messages