[Bug 22129] Allowing @pattern attribute on <input type=number>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22129

--- Comment #9 from Felipe N. Moura <felipenmoura@gmail.com> ---
(In reply to comment #8)
> (In reply to comment #5)
> > It is not exotic formats!
> 
> Sorry, I didn't meant that Brazilian format was exhaustic. I was trying to
> explain that allowing anyone to specify the thousand and decimal separator
> is a door open to allow weird thing and clearly, what we want is:
> thousand={,.'} decimal={,.} decimal != thousand. That's why I meant that
> using lang='something' for those edge cases could be a solution for web
> developers.
> 
> Generally speaking, I do not think the <input type='number'> widget is used
> and supported enough to be able to do that kind of monkey patches on the
> specification for the moment.

I believe the way the input=number works today(even with the pattern attribute)
works for numbers(I mean, integer and float ones, also using "E", etc...) but
for financial date, it is not the best solution(the use of pattern would help,
indeed, but it is not like something being used the way what it was created
for).
That was the reason why I first proposed the idea of having an < input
type="currency" >, avoiding such problems and being more "focused", even for
semantics(let's say that a screen reader could read "one thousand twenty three
dollars and fifty cents" instead of "one thousand twenty three point
five"...HTML5 forms validation and css :invalid state would be a plus!
I believe the "pattern" attribute can really allow weird thing, as mentioned by
Mounir Lamouri, but it is supposed to be used in any type of input, not only in
numbers...then it makes more sense, but still, not the best solution for the
situation we are discussing here...

let me know your thoughts about it :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 24 May 2013 22:58:30 UTC