(12/01/15 6:54), Peta Byte wrote: > + What do you think about my suggestion?
I am neither an implementer nor a member of this list so this is the only question I can answer. > Hello everybody, > > I'm composing an initial mail to the CSS specification mailing list in which > I want to propose the introduction of an additonal TransitionEvent type ... > for now I just call it 'transitionsend'. In contrast to the existing > 'transitionend' event, my suggested one will be fired on an HTMLElement, once > __all__ of its transitioned style properties have reached their final value. The first glance gives me "transition-send", although this is probably just my problem and I don't have better idea. > Rationale > --- > Today, most JS libraries that offer CSS-based tweening/animation > functionality implement this by interval- or requestAnimationFrame-tiggered > (the latter not widely-spread yet) periodical function calls. One of the main > reasons for using CSS3 Transitions is probably the better performance. > Instead of executing a listener function hundred times or more for tweening > an element style, the changes to style property values are calculated and > applied by compiled lower-level code -- what leads to a far better overall > performance. Instead of saying this, the trend in all standards-related lists is to ask you to provide either 1) detailed explanation of "uses cases" or descriptions of various situations why you want this 2) a page (a URL) or more that uses this functionality 3) the JS code that implements this, so you might want to expand this paragraph in advance. And you should be prepared to answer questions like, when should transitionsend occurs in the following situation: |----|----| |--|--|--|--| (a transitionend triggers yet another transition) or in general, what makes a "transitionsend" set? a CSS rule block (examples would certainly help here)? How are the JS libraries you mentioned designed? In general, I don't think you need to compose this e-mail here, and if what I am saying here is making you hesitate to send out this mail then you should really just send this to www-style right away. (Having this discussed there is usually better than having this discussed here, not to mention that implementations differ). I think you should be open minded if your proposal doesn't get good reception. The general principle is that the more thing browser vendors have to implemented the more interoperability related issues they have to face, and Web developers complain about interoperability issues too. You might want to file feature requests on Bugzilla, including the WebKit one, too. Cheers, Kenny _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
