W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2010

Re: New DOM event types

From: João Eiras <joaoe@opera.com>
Date: Tue, 23 Mar 2010 04:53:51 +0100
To: "Jacob Rossi" <rossi@gatech.edu>, www-dom@w3.org
Message-ID: <op.u9z431rp2q99of@coruscant>
On Tue, 23 Mar 2010 04:51:26 +0100, Jacob Rossi <rossi@gatech.edu> wrote:

>> The specification already specifies the 'scroll' event, which is not
>> synchronized with the scrolling action, and not cancelable, being
>> therefore only useful as a notification.
>
> What situation would cause a scroll event to not be synchronized with the
> scrolling action?  I agree that it only serves as a notification. But do  
> we
> really want web pages to be able to prevent a high level UI task such as
> scrolling or zooming?  If I go to scroll the web page and the page  
> cancels
> the beforescroll, how will this not be perceived as unresponsive browser  
> UI?
> Similarly, why would I want to prevent users from zooming the page? I'm  
> not
> sure that's helpful for accessibility either.
>
> Maybe I'm being ignorant of possible use cases for these events to be
> cancelable. But otherwise, I'm not sure I grasp the point of these  
> events.
> Can you provide some example use cases?
>

All that info and responses to your concerns were provided in the first  
e-mail.
Received on Tuesday, 23 March 2010 03:54:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT