- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 Jan 2012 10:36:26 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13531 steve faulkner <faulkner.steve@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |faulkner.steve@gmail.com --- Comment #7 from steve faulkner <faulkner.steve@gmail.com> 2012-01-06 10:36:23 UTC --- (In reply to comment #6) > 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: Rejected > Change Description: no spec change > Rationale: Examples that do not work everywhere yet is not a reason to change > the examples. It's an incentive to get the software fixed. These examples are not for a new feature they are for a feature that has been around for a long time (10+ years): http://www.w3.org/TR/html401/interact/forms.html#h-17.9 In this example, we implicitly associate two labels with two text input controls: <FORM action="..." method="post"> <P> <LABEL> First Name <INPUT type="text" name="firstname"> </LABEL> <LABEL> <INPUT type="text" name="lastname"> Last Name </LABEL> </P> </FORM> Continuing to promote a method that does not work across browsers without at least providing a warning does a disservice to users and developers. Why promote coding practices that don't work cross browser? -- Configure bugmail: https://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 Friday, 6 January 2012 10:38:46 UTC