W3C home > Mailing lists > Public > public-html@w3.org > June 2011

[Bug 12974] New: Allow placeholder="" on <input type=number>

From: <bugzilla@jessica.w3.org>
Date: Thu, 16 Jun 2011 22:17:16 +0000
To: public-html@w3.org
Message-ID: <bug-12974-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12974

           Summary: Allow placeholder="" on <input type=number>
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: eoconnor@apple.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Consider a checkout form on a commerce site. The site wants to use type=number
to trigger a numeric keypad in browsers on devices with on-screen keyboards.
All of the <input type=text> elements in the form have useful placeholder=""
values, so the design of the site and its usability suffer when the type=number
<input>s lack matching placeholder=""s. The placeholder="" attribute is already
supported on <input type=number> in WebKit on iOS, and there is existing
content relying on this feature.

The proposal in http://www.w3.org/Bugs/Public/show_bug.cgi?id=12885 addresses
some related issues, but is a much more sweeping change with no deployed UAs or
content.

I've split this issue out of:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12868

There's a related WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=61095

-- 
Configure bugmail: http://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 Thursday, 16 June 2011 22:17:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:33 GMT