13572 2011-08-03 03:51:46 +0000 4.10.19 aborting autofocus based on user choice not optional 2016-02-26 20:00:06 +0000 1 1 1 Unclassified HTML WG HTML a11y Task Force unspecified PC Windows NT RESOLVED MOVED a11y, a11ytf P2 normal --- 1 cyns cyns chaals cooper faulkner.steve ian laura.lee.carlson lwatson mike public-html-a11y public-html-admin public-html-wg-issue-tracking robin dave.null oldest_to_newest 52083 0 cyns 2011-08-03 03:51:46 +0000 4.10.19 autfocusing a form control “If the user has indicated (for example, by starting to type in a form control) that he does not wish focus to be changed, then optionally abort these steps.” If a user has indicated through a browser, OS, AT or site settting that he doesn't want autofocus behavior, it must not be done. Autofocus is a problem for some AT products, and also for some users who don't understand what has happened. 52627 1 mike 2011-08-04 05:03:16 +0000 mass-moved component to LC1 54641 2 ian 2011-08-10 22:12:06 +0000 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: no spec change Rationale: The spec already says this in the very sentence quoted above. 61991 3 cyns 2011-12-23 20:50:00 +0000 "8.If the user has indicated (for example, by starting to type in a form control) that he does not wish focus to be changed, then optionally abort these steps." Can we remove the word "optionally"? 62156 4 annevk 2011-12-30 11:30:38 +0000 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: We cannot dictate UI. 62161 5 faulkner.steve 2011-12-30 14:20:30 +0000 (In reply to comment #4) > 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: We cannot dictate UI. the spec does dictate UI when you choose to: example: "The alt attribute does not represent advisory information. User agents must not present the contents of the alt attribute in the same way as content of the title attribute." http://dev.w3.org/html5/spec/the-img-element.html#the-img-element 62171 6 annevk 2012-01-01 09:19:38 +0000 I don't think that's quite the same and in any event that should be filed as a different bug if you think it is. 62172 7 faulkner.steve 2012-01-01 15:54:21 +0000 (In reply to comment #6) > I don't think that's quite the same and in any event that should be filed as a > different bug if you think it is. Well, unless explained, your thoughts about them being not quite the same are not supporting your rationale. I am not interested in filing a bug as I was pointing out the flaw in your rationale by providing an example of where you have dictated UI. A MUST requirement that is currently violated by at least one browser. So a precedent has been set. I would suggest that if you want the spec to not dictate UI, you should file a bug. 81483 8 cooper 2013-01-16 14:30:05 +0000 HTML A11Y TF has decided to push this off to HTML.next and ask Cynthia to drive. 81728 9 robin 2013-01-21 15:59:37 +0000 Mass move to "HTML WG" 81846 10 robin 2013-01-21 16:02:22 +0000 Mass move to "HTML WG" 108386 11 lwatson 2014-06-26 15:38:38 +0000 Assigned to Cynthia for further investigation, per HTML A11y TF action 274: http://www.w3.org/WAI/PF/HTML/track/actions/274 125278 12 chaals 2016-02-26 20:00:06 +0000 Moved to https://github.com/w3c/html/issues/105