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 27639 - Value sanitization scheme is untenable.
Summary: Value sanitization scheme is untenable.
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#number-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-17 19:30 UTC by contributor
Modified: 2015-08-13 07:20 UTC (History)
3 users (show)

See Also:


Attachments

Description contributor 2014-12-17 19:30:17 UTC
Specification: https://html.spec.whatwg.org/multipage/forms.html#number-state-(type=number)
Multipage: https://html.spec.whatwg.org/multipage/#number-state-(type=number)
Complete: https://html.spec.whatwg.org/#number-state-(type=number)
Referrer: https://html.spec.whatwg.org/multipage/states-of-the-type-attribute.html

Comment:
Value sanitization scheme is untenable.

Consider following:

<FORM ...>
<INPUT NAME=id TYPE=number>
<INPUT TYPE=SUBMIT>
</FORM>

Q. What happens when user sets value and clicks submit button?

A. Text field "appears" to be blanked concurrently with submit click, user
receives no 
feedback they made a mistake and empty data submitted.

Why does out of range, failure to match pattern or type=email 
afford usable feedback to users?


Posted from: 50.181.209.248
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Comment 1 Ian 'Hixie' Hickson 2014-12-18 01:15:28 UTC
I don't believe what you describe is what the spec requires.