This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10215 - not sure what's mean by "User agents must _synchronously_ run the focusing steps". Does this mean that the event handlers involved in steps 1 and and 3 must return before further steps in the procedure can be taken? A reasonable alternative interpretation
Summary: not sure what's mean by "User agents must _synchronously_ run the focusing st...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-21 03:17 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-07-21 03:17:30 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#focus-management

Comment:
not sure what's mean by "User agents must _synchronously_ run the focusing
steps". Does this mean that the event handlers involved in steps 1 and and 3
must return before further steps in the procedure can be taken? A reasonable
alternative interpretation would be that events get "fired", but the event
handlers don't get invoked until later. This makes sense if firing an event
consists of inserting an event into a queue until the system decides to
dispatch the event, which would happen at some later point.

Posted from: 76.121.107.243
Comment 1 Ian 'Hixie' Hickson 2010-09-08 06:57:04 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Yes, it means running the steps right then and there, without queuing tasks on the event loop. I don't understand how it could be interpreted as "queue a task to fire the event"; if that's what it meant, that's what it would say. If you have any suggestion for better text, please let me know.