- From: <bugzilla@jessica.w3.org>
- Date: Tue, 11 Feb 2014 12:23:24 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13553 --- Comment #6 from steve faulkner <faulkner.steve@gmail.com> --- So re-reading again - the preceding sentence to the one quoted states: "If the for attribute is not specified, but the label element has a labelable element descendant, then the first such descendant in tree order is the label element's labeled control." http://www.w3.org/html/wg/drafts/html/master/forms.html#the-label-element which covers the test case I put in the previous comment. the intent of the second sentence is to cover this case (i believe) <label>Lost <input type=text name=lost id="lost"> </label> <label for="lost">found <input type=text name=found id="found"> </label> See Ian's Comment 2 "The sentence is question is required to make sure that if you click on a text field inside a <label> whose labeled control is another text field, you don't end up focusing the other text field (which would be rather confusing to users)." from testing FF/IE/Chrome on windows 8, the behaviour is consistent, clicking on the second label focuses the first control, which appears contrary to what the spec is trying to stop. what appears to be the case for the browsers tested is that for/id labelling overrides nested control labeling. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 11 February 2014 12:23:27 UTC