- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 17 Feb 2010 12:26:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8722 steve faulkner <faulkner.steve@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NEEDSINFO | --- Comment #6 from steve faulkner <faulkner.steve@gmail.com> 2010-02-17 12:26:09 --- (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: 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? take the AT out of the example: I am using a browser, as I tab through focusable elements the focus moves to the next element , if that element is out of view before it receieves focus, it gets moved into view. This is the behaviour for all browsers I have tried. Why should this not be the same for focusable elements on the canvas? where is it specified for other elements that this behaviour is optional? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 17 February 2010 12:26:11 UTC