{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 可以哭但决不认输i 的问题《Clean way to programmatically use CSS transitions》','https://www.manongdao.com/q-93505.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
As the title implies, is there a proper way to set some initial CSS properties (or class) and tell the browser to transition these to another value?
For example (fiddle):
var el = document.querySelector('div'),
st = el.style;
st.opacity = 0;
st.transition = 'opacity 2s';
st.opacity = 1;
This will not animate the opacity of the element in Chrome 29/Firefox 23. This is because (source):
[...] you’ll find that if you apply both sets of properties, one immediately after the other, then the browser tries to optimize the property changes, ignoring your initial properties and preventing a transition. Behind the scenes, browsers batch up property changes before painting which, while usually speeding up rendering, can sometimes have adverse affects.
The solution is to force a redraw between applying the two sets of properties. A simple method of doing this is just by accessing a DOM element’s
offsetHeightproperty [...]
In fact, the hack does work in the current Chrome/Firefox versions. Updated code (fiddle - click Run after opening the fiddle to run animation again):
var el = document.querySelector('div'),
st = el.style;
st.opacity = 0;
el.offsetHeight; //force a redraw
st.transition = 'opacity 2s';
st.opacity = 1;
However, this is rather hackish and is reported to not work on some android devices.
Another answer suggests using setTimeout so the browser has time to perform a redraw, but it also fails in that we don't know how long it will take for a redraw to take place. Guessing a decent number of milliseconds (30-100?) to ensure that a redraw occurred means sacrificing performance, unnecessarily idling in the hopes that the browser performs some magic in that little while.
Through testing, I've found yet another solution which has been working great on latest Chrome, using requestAnimationFrame (fiddle):
var el = document.querySelector('div'),
st = el.style;
st.opacity = 0;
requestAnimationFrame(function() {
st.transition = 'opacity 2s';
st.opacity = 1;
});
I assume that requestAnimationFrame waits until right before the beginning of the next repaint before executing the callback, hence the browser does not batch up the property changes. Not entirely sure here, but works nicely on Chrome 29.
Update: after further testing, the requestAnimationFrame method does not work very well on Firefox 23 - it seems to fail most of the time. (fiddle)
Is there a proper or recommended (cross-browser) way of achieving this?
Here's a working version. See it yourself.
Tested on Chrome, Firefox, Opera.
On my version of firefox, it does not support style.transition so I made it to fallback to vendor specific name if standard name is not available.
http://jsfiddle.net/eNCBz/5/
Let me explain what is going on:
made some helper functions like ucfirst, toCamelCase
try to find vendor specific style property name if standard name is not available
utilize setTimeout function to make sure browser to redraw
I tried to make it more generic function so other properties can be applied as well, such as color or background.
Hope this helps!
There isn't a clean way at this moment (without using CSS Animations -- see the nearby answer by James Dinsdale for an example using CSS Animations). There is a spec bug 14617, which unfortunately wasn't acted upon since it was filed in 2011.
setTimeoutdoes not work reliably in Firefox (this is by design).I'm not sure about
requestAnimationFrame-- an edit to the original question says it doesn't work reliably either, but I did not investigate. (Update: it looks likerequestAnimationFrameis considered at least by one Firefox core developer to be the place where you can make more changes, not necessarily see the effect of the previous changes.)Forcing reflow (e.g. by accessing
offsetHeight) is a possible solution, but for transitions to work it should be enough to force restyle (i.e.getComputedStyle): https://timtaubert.de/blog/2012/09/css-transitions-for-dynamically-created-dom-elements/Note that just running
getComputedStyle(elem)is not enough, since it's computed lazily. I believe it doesn't matter which property you ask from the getComputedStyle, the restyle will still happen. Note that asking for geometry-related properties might cause a more expensive reflow.More information on reflow/restyle/repaint: http://www.phpied.com/rendering-repaint-reflowrelayout-restyle/
The situation has changed since 2013, so here's a new answer:
You could use Web Animations. They are implemented natively in Chrome 36 and Firefox 40 and there is a polyfill for all the other browsers.
Example code:
#
You shouldn't need too much JavaScript to achieve what you want, just use CSS keyframes and animations for the same effect.
As shown in this JsFiddle it works either from page load (with class already added) or when dynamically adding the class to trigger the animation.