This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"Let control be the first element in tree order whose nearest ancestor dialog element is subject and that has an autofocus attribute specified, if any." modify this so that focus moves by default(does not need author to do). this will make it much better for keyboard/screen reader/screen mag users.
Commit pushed to master at https://github.com/w3c/html https://github.com/w3c/html/commit/210ea0850ab98bc566f575f4a7913074ea88b6b2 make focus move to dialog see bug 23365
rationale: currently moving focus to a dialog relies upon the author setting autofocus on one of the focusable elements in the dialog. As we know authors don't often think about keyboard interaction and if autofocus is not set it will 9as it is currently with custom dialogs) be problematic for SR,keyboard users and screen mag users.
see chrome bug - http://code.google.com/p/chromium/issues/detail?id=264959
""Let control be the first focusable element in tree order whose nearest ancestor dialog element is subject or that has an autofocus attribute specified." Maybe it should be more explicit that autofocus has priority?
(In reply to Matt Falkenhagen from comment #4) > ""Let control be the first focusable element in tree order whose nearest > ancestor dialog element is subject or that has an autofocus attribute > specified." > > Maybe it should be more explicit that autofocus has priority? agree since the statement form is "x or y" then the statement is true whenever x is true, so it can be read as focus first focusable control, otherwise focus unfocusable element having autfocus attribute. Also, a note, if the change concerns to modal dialogs only then it's probably fine since modal dialogs must take focus always but it'd double check that.
(In reply to alexander surkov from comment #5) > (In reply to Matt Falkenhagen from comment #4) > > ""Let control be the first focusable element in tree order whose nearest > > ancestor dialog element is subject or that has an autofocus attribute > > specified." > > > > Maybe it should be more explicit that autofocus has priority? > > agree since the statement form is "x or y" then the statement is true > whenever x is true, so it can be read as focus first focusable control, > otherwise focus unfocusable element having autfocus attribute. True though what I was worried more about is ambiguity over whether the first element in tree order or an element with autofocus gets focus.
reverted commit, leaving it up to the acc engineers to work it out with hixie
(In reply to steve faulkner from comment #7) > reverted commit, leaving it up to the acc engineers to work it out with hixie how it could be wontfix if the fix was landed (comment #1)? Honestly I'm getting confused with number of bugs related to dialog element we have.
(In reply to alexander surkov from comment #8) > (In reply to steve faulkner from comment #7) > > reverted commit, leaving it up to the acc engineers to work it out with hixie > > how it could be wontfix if the fix was landed (comment #1)? Honestly I'm > getting confused with number of bugs related to dialog element we have. i reverted the fix
so the reason of wontfix is as soon as twin WHATWG bug is fixed then the change automatically goes into W3C spec. Correct?
(In reply to alexander surkov from comment #10) > so the reason of wontfix is as soon as twin WHATWG bug is fixed then the > change automatically goes into W3C spec. Correct? when/if the whatwg commit comes along unless anybody objects it will be committed to the HTML spec.
(In reply to steve faulkner from comment #9) > (In reply to alexander surkov from comment #8) > > (In reply to steve faulkner from comment #7) > > > reverted commit, leaving it up to the acc engineers to work it out with hixie > > > > how it could be wontfix if the fix was landed (comment #1)? Honestly I'm > > getting confused with number of bugs related to dialog element we have. > > i reverted the fix > Honestly I'm > getting confused with number of bugs related to dialog element we have. that's why i closed this one.
FYI: adopted commits from WHATWG: https://github.com/w3c/html/commit/49968eba023dc0d9b74ded165f29e37cfbf0ac81 and https://github.com/w3c/html/commit/e45d2cbeb7f242aec1825958beb1e552753c7cf2
Commit pushed to CR at https://github.com/w3c/html https://github.com/w3c/html/commit/210ea0850ab98bc566f575f4a7913074ea88b6b2 make focus move to dialog