W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: Proposal for mousewheel events

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Mon, 10 Apr 2006 17:29:14 -0500
Message-ID: <443ADC3A.8020608@mit.edu>
To: Sjoerd Visscher <sjoerd@w3future.com>
CC: public-webapi@w3.org

Sjoerd Visscher wrote:
>>> But a *synchronous* call does block the running javascript thread, 
>>> and no redraws happen in between.
>>
>> The statement after the comma is false.
> 
> At least it is not visible. Except when you do things like an alert.

You need a server that takes longer to respond to the XMLHttpRequest.  Try 
having it take 3-4 minutes to respond and see what things look like.  ;)

>> Single-threadedness and non-reentrancy are not the same thing, fwiw.
> 
> Ok, then I mean non-reentrancy.

That's already somewhat broken.  For example, I bet mouse move events can fire 
during synchronous XMLHttpRequest calls.

> I don't want to argue about the details here. There is *something* in 
> Firefox that prevents layout and painting in the simple cases

Other than the fact that layout and painting usually happen off events, nothing. 
And there are programmatic ways to force layout to happen without an event. 
Possibly also for painting if one tries hard enough.

> which should be good enough for doing smooth diagonal scrolling with 2 
> separate events.

Not really, no.  At least not if you actually want it to work in general.

-Boris
Received on Monday, 10 April 2006 22:29:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT