- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Jun 2011 20:52:34 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13099 Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Simetrical+w3cbug@gmail.com Resolution| |NEEDSINFO --- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-06-30 20:52:33 UTC --- 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: Additional Information Needed Change Description: no spec change Rationale: Per comment 1, we already have a mechanism for this, which relies on a convention that long predates the placeholder attribute. Is there something specifically wrong with it that would justify supporting a redundant mechanism to do the same thing? -- 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 Thursday, 30 June 2011 20:52:35 UTC