12-08-2012 03:21 PM
Hello
I have a HTML5 element defined as follows:
<input type="number" min="0.01" step="any" name="foo"/>
When I click on it via BB10 Dev Alpha (10.0.9.1103), I get numeric keyboard (which is good), but without decimal points (which is very bad).
According to http://www.w3.org/TR/html-markup/input.number.html floating numbers should be accepted.
On Playbook (2.1.0.1088), the behaviour is even weirder, because it shows me numeric keyboard for a milisecond and then changes to the full one
Is it going to be resolved soon, or we are stuck with input type="text" and JS validation on input?
12-10-2012 09:14 AM
Hello,
I'm checking into this. I'll report back as soon as I have news.
Thanks!
12-10-2012 09:19 AM
So it looks like yes, the teams are aware of this issue and are working towards correcting it.
12-10-2012 01:11 PM
Great!
If we're on this topic, this "numeric keypad" should be completely changed for a web view. If you're aware of all these, then very good! But I'd like to have a full reference here anyway to avoid creating new tickets for the same issue ![]()
In fact input type="number" doesn't allow hexadecimal (A-F) and should allow,besides decimal point, minus ("-") sign (if "min" attribute is set to a non-negative number).
Here's the full definition from W3 data type reference:
A floating-point number consists of the following parts, in exactly the following order:
01-01-2013 10:56 AM
until now with the updated OS this hasn't been resolved
01-04-2013 07:19 AM
I reported this a long time ago in the playbook, too bad its also like this in bb10 ![]()
01-04-2013 08:32 AM
how do you report the problem so I can also make a report, I had to make a script to validate the user input the old fashioned way becuase input type-number doesn't have a decimal place
01-04-2013 09:02 AM
I think I did it via github at the time...
you can use some javascript functions like isNaN() to help you workaround it.
01-26-2013 10:00 AM
Just wondering if anyone knows if this has been fixed yet in the latest BB10 betas? I don't have a BB10 device, I have a Playbook on OS 2.1 and this issue is a little annoying.
01-26-2013 12:13 PM
The issue is being tracked, there's no update just yet but I'll follow-up with them.