- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 5 Oct 2011 09:30:18 -0700
- To: divya manian <divya.manian@gmail.com>
- Cc: Sylvain Galineau <sylvaing@microsoft.com>, Brian Manthos <brianman@microsoft.com>, "L. David Baron" <dbaron@dbaron.org>, Boris Zbarsky <bzbarsky@mit.edu>, "www-style@w3.org" <www-style@w3.org>
On Wed, Oct 5, 2011 at 9:03 AM, divya manian <divya.manian@gmail.com> wrote: > On Tuesday, October 4, 2011, Tab Atkins Jr. wrote: >> Precisely. JS animations work over specified values, but the >> principle is the same. You know what the values are, and in the case >> of the display:none element itself, you're not fighting against >> performance optimizations either. > > What is the use case for animating elements that are display none? One I can > think of would be to somehow use CSS animations to update (generated) > content on a page and then by setting display to none, you would be > disrupting the update of the content. But it seems like a terrible hack to > do this in any case. For example, running an animation on some content within a <details> that stays consistent when you open/close the element. Unfortunately, that's probably the "subtree" case that's harder to deal with. ~TJ
Received on Wednesday, 5 October 2011 16:31:13 UTC