Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.straub-nv.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Content-Type: text/plain; charset="UTF-8"
Message-ID: <2010653.qWjjvXNv77@PointedEars.de>
From: Thomas 'PointedEars' Lahn <PointedEars@web.de>
Reply-To: Thomas 'PointedEars' Lahn <usenet@PointedEars.de>
Organization: PointedEars Software (PES)
Date: Sun, 20 Jan 2013 04:46:41 +0100
User-Agent: KNode/4.4.11
Content-Transfer-Encoding: 8Bit
Subject: Re: Why is this not working
Newsgroups: comp.lang.javascript
References: <kdei12$7eg$1@dont-email.me> <nurlf8ht64qtqghh478a7mjrtfqceknvfe@4ax.com> <7309657.PzdHBbrMY6@PointedEars.de> <r37mf85tplqvog2pfi90cejhkqnje2pori@4ax.com> <kdfikk$65r$1@news.albasani.net> <1840215.6M2mspuZ93@PointedEars.de> <kdfogm$hg2$1@news.albasani.net>
Followup-To: comp.lang.javascript
MIME-Version: 1.0
Lines: 39
NNTP-Posting-Date: 20 Jan 2013 04:46:42 CET
NNTP-Posting-Host: 696b1285.newsspool4.arcor-online.net
X-Trace: DXC=]\Z@eoN1@dV5TOT9_N5i<V4IUK<Cl32<Q4Fo<]lROoRQ8kF<OcfhCO[?F<P;FJ26_RDZm8W4\YJN\b@mF9jNikdUe8nA28^e?>RI=?2ce78[;Y
X-Complaints-To: usenet-abuse@arcor.de
Xref: csiph.com comp.lang.javascript:18158

Stefan Weiss wrote:

> 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".

Your logic is flawed as you are trying to shift the burden of proof.  You 
were to prove that “practically all current JS-capable browsers display this 
behavior”, not I that this is not true.  Probably someone has told you this 
before.

> 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.

Doubtful.

> PS, didn't you killfile me in November "for a longer time"? Just in case
> your filter got confused, please re-add me.

So that you can have it your way and continue spouting nonsense?  No.
(New year, new scorefile rules.)

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.