You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wait a little longer for the highlight element to take it's initial state. If
the element is not yet in its initial state, the transition does not happen. It
seems like on Firefox/Gecko it takes longer than on Chrome/Webkit.
Care should also be taken when using a transition immediately after adding the element to the DOM using .appendChild() or removing its display: none; property. This is seen as if the initial state had never occurred and the element was always in its final state. The easy way to overcome this limitation is to apply a window.setTimeout() of a handful of milliseconds before changing the CSS property you intend to transition to.
Comment by busykai Friday Dec 12, 2014 at 17:40 GMT
@cheesypoof, thanks for the reference. I'll look into it to see if our code could be reorganized. From the looks of it, it sounds like that FF does not do appendChild synchronously hence requiring a tangible wait period (well, 20ms is not perceivable, but still longer than just yielding). The issue was still reproducible with the Aurora latest versions (~FF 36).
Issue by busykai
Thursday Dec 11, 2014 at 18:34 GMT
Originally opened as adobe/brackets#10151
Fixes #10142.
Wait a little longer for the highlight element to take it's initial state. If
the element is not yet in its initial state, the transition does not happen. It
seems like on Firefox/Gecko it takes longer than on Chrome/Webkit.
This is a quote from MDN article on subject:
CC:
@
dangoor,@
redmundsbusykai included the following code: https://github.com/adobe/brackets/pull/10151/commits
The text was updated successfully, but these errors were encountered: