[whatwg] A few editing suggestions for the HTML5 spec

[Kristof Zelechovski]

Methinks, if several buttons are pressed, the events should be placed in the
queue and executed in the order of appearance.  If the page is reloaded as a
result of an event handler, all remaining events should be discarded as
usual.
I am not quite sure how to handle this situation because the user could end
up pressing all of the buttons out of impatience in search for a button that
"works".  It is irrelevant if the first button pressed causes a reload,
otherwise the result may not meet the user's expectation.  The user agent
should indicate its busy state with an hourglass pointer, a status message,
an animated icon, whatever in order to prevent this misunderstanding.
Chris

-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Geoffrey Garen
Sent: Sunday, April 15, 2007 8:32 PM
To: Kristof Zelechovski
Cc: whatwg at whatwg.org
Subject: Re: [whatwg] A few editing suggestions for the HTML5 spec

> Pressing a button when the user agent is in paused state should  
> cause the
> button to remain pressed until the user agent wakes up and  
> execution of the
> associated event handlers should be deferred.

So, if I had N buttons in a page, does that mean that all N could  
potentially end up in a pressed state?

Geoff