- From: <bugzilla@jessica.w3.org>
- Date: Sun, 11 Jul 2010 15:58:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9670
Alexandre Alapetite <alexandre@alapetite.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexandre@alapetite.fr
--- Comment #3 from Alexandre Alapetite <alexandre@alapetite.fr> 2010-07-11 15:58:09 ---
Hello,
I am also hit by this bug.
More generally, I believe that @size and @maxlength should be allowed on input
of @type {Date and Time, Date, Month, Week, Time, Local Date and Time, Number,
Range, Color, File Upload}, in addition to the ones already allowed {Text,
Search, URL, Telephone, E-mail, Password}.
See
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#input-type-attr-summary
A simple approach would be that @size and @maxlength could be allowed, while
other values would take precedence when the @type values are properly
implemented in a given browser.
But I believe a better approach would be to use all of them (@size, @maxlength,
@max). This seems to be Opera's approach. In the example of @type=number,
@maxlength is needed to put a boundary on the number of decimals (e.g. "0.001"
is ok but not "0.0001" when @maxlength=5). If the most typical values are small
(e.g. 3 digits), but sometimes may be large, then @size is useful to define how
many digits are visible at a time.
Best regards,
Alexandre
http://alexandre.alapetite.fr
--
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 Sunday, 11 July 2010 15:58:12 UTC