W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2016

[csswg-drafts] [css-transitions] transitionstart definition does not match Edge behavior

From: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Mon, 22 Aug 2016 02:15:44 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-172357453-1471832142-sysbot+gh@w3.org>
birtles has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-transitions] transitionstart definition does not match Edge 
behavior ==
CSS Transitions Level 2 defines the [transitionstart 
event](https://drafts.csswg.org/css-transitions-2/#eventdef-transitionevent-transitionstart)
 as being fired "when a transition is started (i.e., when it is added 
to the set of running transitions)".

However, Edge is [already shipping a transitionstart 
event](https://msdn.microsoft.com/library/dn632683(v=vs.85).aspx) that
 fires at the end of the delay as demonstrated in this fiddle: 
https://jsfiddle.net/jph4eo2o/

Making `transitionstart` fire at the end of the delay is consistent 
with `animationstart`. However, it is less useful for authors who want
 to determine whether a given style change triggered the creation of a
 new transition or not (e.g. so they know if they should wait for 
`transitionend` events before considering the element to be in a 
stable state).

Perhaps we need a separate event for when a transition is created, 
`transitionfire` or something of the sort?


Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/416 using your GitHub 
account
Received on Monday, 22 August 2016 02:15:52 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:22 UTC