Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!news.albasani.net!news.mb-net.net!open-news-network.org!.POSTED.100.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: Re: CSS transition Date: Wed, 23 Aug 2017 14:51:19 +0200 Organization: PointedEars Software (PES) Lines: 38 Message-ID: <1745316.usQuhbGJ8B@PointedEars.de> References: Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit Injection-Info: gwaiyur.mb-net.net; posting-host="100.225.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch:178.197.225.100"; logging-data="27730"; mail-complaints-to="abuse@open-news-network.org" User-Agent: KNode/4.14.2 X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. However, you won't get a smooth animation by changing the 'left' (or > top, right, bottom) property, because it will trigger a reflow process > in the browser [1]. There is no reason why it should, and in fact the referred blog entry does not claim this. “Reflow” pertains to the rearrangement of elements in the document flow. With `position: absolute`, an element is *taken out* of the document flow. What will happen is “repaint”, but that will happen in any case. > […] > Another possibility is using the fresh Web Animations API [2], i.e > Element.animate(), supported by some modern browsers so far. Interesting. > […] > [1] > This is from 2012-12-20. The update referred there is from 2016. We have 2017-08 now. Be suspicious of any Web development advice that is older than one year. While the advice does not change, layout engines keep being improved. With “rapid release” schedules, the advice from last month can already be out of date. (That is also why it is a bad idea to rely on books in this field.) > [2] -- PointedEars FAQ: | | Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.