This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12974 - Allow placeholder="" on <input type=number>
Summary: Allow placeholder="" on <input type=number>
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: contributor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-16 22:17 UTC by Edward O'Connor
Modified: 2012-02-06 13:14 UTC (History)
8 users (show)

See Also:


Attachments

Description Edward O'Connor 2011-06-16 22:17:16 UTC
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
Comment 1 Ian 'Hixie' Hickson 2011-06-16 22:34:19 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2011-06-16 22:34:34 UTC
Checked in as WHATWG revision r6248.
Check-in comment: Add placeholder='' support to type=number.
http://html5.org/tools/web-apps-tracker?from=6247&to=6248
Comment 3 Julian Reschke 2011-06-17 06:55:30 UTC
New feature. Not discussed in HTML WG. Please revert.
Comment 4 Ms2ger 2011-06-17 07:11:56 UTC
Oversight when first specifying placeholder. No new feature. Objection to reverting.
Comment 5 Edward O'Connor 2011-06-17 16:38:11 UTC
This isn't a new feature, it's a simple, small bug in an existing feature, present since that feature (the placeholder="" attribute) was first added to the spec in 2008. I raised this issue in the HTML WG, following to the HTML WG Decision Policy, by filing a bug. This is the standard procedure in the HTML WG for bringing an issue to the editor's attention.

Julian, do you have a technical objection to this change? If so, could you state it?

The Decision Policy states that during Last Call "we *don't want to call a total stop* to useful changes[] But that might create a situation where a person or group *strongly* objects to some change[] If any Working Group member sees a change go in[] that seems controversial and likely to reduce rather than increase consensus, the correct step is to let the Chairs know, ideally via a post to the public list." (Emphasis mine.) Julian, do you strongly object to this change? Do you believe that this change is "controversial and likely to reduce rather than increase consensus?" I note also that the Decision Policy states that "[w]e do not expect [the enhanced change control] process to be used casually over random changes."
Comment 6 Ian 'Hixie' Hickson 2011-06-21 07:31:05 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: Rejected
Change Description: no spec change
Rationale: see comment 4 for rejection to comment 3, comment 0 for original rationale for inclusion.
Comment 7 Aryeh Gregor 2011-06-22 20:54:02 UTC
You just closed this bug WONTFIX, which I assume wasn't intended, since placeholder is still in the spec.  Maybe you meant to reclose it FIXED?
Comment 8 Ms2ger 2011-06-23 07:13:44 UTC
The reversion request was wontfixed, but yes, the original bug is still fixed.
Comment 9 Michael[tm] Smith 2011-08-04 05:15:23 UTC
mass-move component to LC1