- From: <bugzilla@jessica.w3.org>
- Date: Fri, 10 Feb 2012 18:48:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15953 Summary: Section title: "The placeholder attribute" "User agents should present this hint to the user, after having stripped line breaks from it, when the element's value is the empty string and the control is not focused (e.g. by displaying it inside a blank unfo Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Specification: http://www.w3.org/TR/html5/spec.html Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Section title: "The placeholder attribute" "User agents should present this hint to the user, after having stripped line breaks from it, when the element's value is the empty string and the control is not focused (e.g. by displaying it inside a blank unfocused control)." Usability would be improved if the wording was changed to ensure that the placeholder remained visible when the control was focussed. Placeholder text often contains information that is helpful to the user when filling out the control. This should remain visible until the last possible moment (i.e. when the user starts typing.) Suggested rewording: "User agents should present this hint to the user, after having stripped line breaks from it, when the element's value is the empty string (e.g. by displaying it inside a blank unfocused control)." Posted from: 81.100.168.129 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7 -- 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, 10 February 2012 18:48:11 UTC