[Bug 9670] New: Allow "size" attribute for input-type "number"

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9670

           Summary: Allow "size" attribute for input-type "number"
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: a.kuckartz@ping.de
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


The text below is copied from http://bugzilla.validator.nu/show_bug.cgi?id=741

***

Thanks. I now agree that "validator.nu behavior for this case
conforms to the current spec". I had not expected such a backwards
compatibility problem.

I think that this is a problem in the specification because (as far as I know)
legacy browsers do not know what to do with min and max attributes.

So I either use input-type text with the size attribute which is supported by
legacy browsers and HTML5 or I use inputtype number which is supported by HTML5
but where the size can not be specified.

This makes it difficult to migrate from old-HTML to HTML5.

Maybe this can be forwarded to those who care about this aspect of the
specification?

I agree with what someone else wrote on that problem:

"A) What happens when your type=number has no min or max but you know how many
digits it should fit? B) What happened to backwards compatibility? HTML5 inputs
were supposed to be backwards compatible. type=number inputs fall back to
type=text inputs when the browser has not implemented number inputs yet. text
input size has always been controlled using size= (and css of course) and
min/max/step values will have no effect on browsers that haven't implemented
number. So if type=number is supposed to fallback to type=text why is it that
including a size= attribute so that the text fallback doesn't get insanely long
makes your html5 document invalid? Shouldn't size= be listed as "do not apply"
rather than "must not be specified, ..."?"

http://blog.danielfriesen.name/2010/04/20/html5-number-input-implementation-flops/

-- 
Configure bugmail: http://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 Thursday, 6 May 2010 13:49:46 UTC