- From: <bugzilla@jessica.w3.org>
- Date: Sun, 22 Apr 2012 19:09:48 +0000
- To: public-html@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16817 Summary: What's the difference between input/@title's and input/@placeholder's semantic? Both of them act as the user's advisor and tell you what you can do with the element. "For a longer hint [...], the title attribute is more appropriate." is the only thing I c 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: Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: What's the difference between input/@title's and input/@placeholder's semantic? Both of them act as the user's advisor and tell you what you can do with the element. "For a longer hint [...], the title attribute is more appropriate." is the only thing I could read about. If there's (another) difference, it would be fine to describe it. If @placeholder is just physical markup (that's what the attribute's confusing name denotes), then I think it would be better to present @title like a placeholder using stylesheets instead of specifing a new attribute called @placeholder. Posted from: 178.191.160.147 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.140 Safari/535.19 Comodo_Dragon/18.0.3.0 -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 24 April 2012 14:30:21 UTC