Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #18157
| From | Stefan Weiss <krewecherl@gmail.com> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Why is this not working |
| Date | 2013-01-20 04:32 +0100 |
| Organization | albasani.net |
| Message-ID | <kdfogm$hg2$1@news.albasani.net> (permalink) |
| References | (1 earlier) <nurlf8ht64qtqghh478a7mjrtfqceknvfe@4ax.com> <7309657.PzdHBbrMY6@PointedEars.de> <r37mf85tplqvog2pfi90cejhkqnje2pori@4ax.com> <kdfikk$65r$1@news.albasani.net> <1840215.6M2mspuZ93@PointedEars.de> |
On 2013-01-20 03:08, Thomas 'PointedEars' Lahn wrote: > Stefan Weiss wrote: >> In a typical browser, it's not just too fast to see, but impossible to >> see: the display will only be updated (re-rendered) after the script has >> run its course. > > The behavior is implementation-dependent; there is nothing ”typical” > about it. And the word you were looking for was “reflow”. This behavior is an optimization, so of course it's implementation dependent. Practically all current JS-capable browsers display this behavior, hence "typical". Prove that a significant percentage of browsers work differently, and I'll retract "typical". The word I intended is "rerender" (aka "repaint"). Reflows can happen several times between display updates, but they are not visible to the user until the display is updated (rerendered, repainted). Nothing in the given example forces a reflow until the final display update. - stefan PS, didn't you killfile me in November "for a longer time"? Just in case your filter got confused, please re-add me.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Why is this not working "Tony Johansson" <johansson.andersson@telia.com> - 2013-01-19 17:35 +0100
Re: Why is this not working Tim Streater <timstreater@greenbee.net> - 2013-01-19 16:52 +0000
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-19 18:45 +0100
Re: Why is this not working Martin Leese <please@see.Web.for.e-mail.INVALID> - 2013-01-19 10:17 -0700
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-19 18:26 +0100
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-19 18:50 +0100
Re: Why is this not working Richard Yates <richard@yatesguitar.com> - 2013-01-19 11:11 -0800
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-19 21:17 +0100
Re: Why is this not working Richard Yates <richard@yatesguitar.com> - 2013-01-19 14:30 -0800
Re: Why is this not working Stefan Weiss <krewecherl@gmail.com> - 2013-01-20 02:52 +0100
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-20 03:08 +0100
Re: Why is this not working Stefan Weiss <krewecherl@gmail.com> - 2013-01-20 04:32 +0100
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-20 04:46 +0100
Re: Why is this not working Danny <dann90038@gmail.com> - 2013-01-19 12:42 -0800
Re: Why is this not working "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-19 22:53 +0100
Re: Why is this not working Jeff North <jnorthau@yahoo.com.au> - 2013-01-20 15:13 +1100
Re: Why is this not working Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-20 06:45 +0100
Re: Why is this not working Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-01-20 18:20 +0000
csiph-web