- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 28 Apr 2010 03:54:45 -0400
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: www-style list <www-style@w3.org>
On 4/28/10 2:29 AM, Brad Kemper wrote: > I don't understand. The transition has to start sometime. Yes. > So the first thing it does is get the offsetHeight to transition from. Which might well give different results in different browsers, or even in the same browser depending on memory layout. At least if implemented the way you just described. For example, if a browser batches up style changes and processes the batch all at once, the transition will start partway through the processing of the batch. At this point, some of the pending style changes have been processed and some haven't; which ones have or haven't may well be effectively random. Is the idea that all change processing needs to complete before sampling the "auto" height the transition should run to? Something else? > It may not be perfect, but it would be better than me trying to set a fixed height on everything I wanted to transition this way (and I could still do that anyway, if I liked it better). Honestly, my feeling on this is the same as the webkit developer who commented earlier in this thread. The moment such a thing is implemented, people will start demanding that various corner cases "work correctly", and work the same way in different browsers, etc. It sounds like a huge time-and-effort-sink... -Boris
Received on Wednesday, 28 April 2010 07:55:20 UTC