This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec currently states: "The blur() method, when invoked, should run the focusing steps for the body element, if there is one; if there is not, then it should run the unfocusing steps for the element on which the method was called instead. User agents may selectively or uniformly ignore calls to this method for usability reasons." I think examples where calls of the blur() method need to be ignored should be given. It would help to reinforce correct use, rather that the assumption that the reader inherently understands good usability practice.
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: Did Not Understand Request Change Description: no spec change Rationale: Do you have any suggestions?
Thanks to Gez for the following example: There can be usability issues using the JavaScript blur method. Some designers don't like the dotted rectangle that some browsers place around the link that currently has focus (either from tabbing to the link, or clicking through a link and then pressing the back button). This dotted rectangle is an aid for keyboard only users to give some kind of visual indication that an element has focus, but some designers only focus on the mode they're familiar with; using the mouse to navigate, and rarely think about keyboard only users. Some of these designers use the blur technique to remove focus so that the dotted line is removed so as not to ruin their design with something like: <a href="..." onfocus="this.blur()">...</a> The problem with this is that this method effectively renders the page useless for keyboard users, as it's impossible to navigate to or go past that link using the keyboard, as the blur method deliberately removes focus from the element. That could be a typical example that a user agent would ignore for usability, as this kind of behaviour is not beneficial.
Thanks! 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments
Checked in as WHATWG revision r4733. Check-in comment: Elaborate on why blur() is bad. http://html5.org/tools/web-apps-tracker?from=4732&to=4733
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq6 Spec is now consistent with the change request in this bug.