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

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

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 Mar 2011 13:46:15 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q5ICV-00038c-3v@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9670

Ross Nicoll <jrn@jrn.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #5 from Ross Nicoll <jrn@jrn.me.uk> 2011-03-31 13:46:11 UTC ---
The "size" attribute however is needed as a rendering hint, and cannot always
be inferred correctly. It may need to be shorter than the maximum possible
value, for example if rendering a data table where horizontal space is at a
premium (this is the case that I'm looking at). It might also want to be longer
than the maximum possible value, for example to match width of other fields in
the same form, for appearance purposes.

I suppose theoretically it could be sized using CSS, but surely if that's the
correct response there's no need for the "size" attribute anywhere? It would
seem a lot more straight forward to remove the explicit disallowing of "size"
on number fields. Firefox & Chrome I believe both implement this anyway (Opera
does mis-render such fields, though).



With respect to the "maxlength" attribute, I think it is okay to infer from
other attributes. In theory it might be important if the data is stored
server-side to a certain number of significant digits, rather than by min/max &
scale, but that seems an odd case.

-- 
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, 31 March 2011 13:46:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 March 2011 13:46:26 GMT