- From: <bugzilla@jessica.w3.org>
- Date: Mon, 29 Aug 2011 04:41:39 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13942 Summary: Allow @autofocus on any element with @tabindex Product: HTML WG Version: unspecified Platform: PC URL: http://dev.w3.org/html5/spec/editing#focus OS/Version: All Status: NEW Keywords: a11y Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: xn--mlform-iua@xn--mlform-iua.no QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Created attachment 1026 --> http://www.w3.org/Bugs/Public/attachment.cgi?id=1026 Demo page (the demo immitates a frameset page) ISSUE: * @autofocus is currently permitted only on 5 elements: button; input; keygen; select; textarea * HOWEVER, javascript is used to set focus also on other elements. One usecase can be elements that imitated a frame: If the main content of the page is kept inside that element, then authors would like to give focus to that element, so that the user can start to scroll the page by pressing the SPACE key. * Of course, it must continue to only be permitted to have a single @autofocus per page. EXAMPLE PAGE: (also available as attachment): http://tinyurl.com/4xy4nr8 ADVANTAGES: Currently, one must use javascript to do this. This means that autofocus can't be set whenever javascript is disabled or when the author is unfamiliar with javascript. DISADVANTAGE OF CURRENT SITUATION: If a page contains e.g. a <button autofocus> element, the author might still use javascript to give focus to another element than the one with @autofocus set - making @autofocus virtually useless. But, if autofocus could be used to give focus to any element with @tabindex, then the author is more likely to keep @autofocus and javascript in sync (e.g. if he/she uses javascript to target legacy browsers). -- 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 Monday, 29 August 2011 04:41:40 UTC