- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 17 Feb 2010 11:56:01 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8722 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |NEEDSINFO --- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-02-17 11:56:00 --- 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: looking for further clarification Suppose an AT allowed the user to make the focus track the mouse pointer, or follow the keyboard focus, and that the user could switch from one to the other. (This may or may not be a good idea, that's rather academic. There could be one user who prefers this, in which case he might write such an AT himself.) Given such a situation, do you think the user agent would have to be defined as _non-conforming_ if it respected that user option, and _didn't_ move the magnifier when the user was in the "follow mouse" mode rather than the "follow focus" mode? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 17 February 2010 11:56:02 UTC