Hi Jeffrey,
Ok, well the iPad is updated.
I'm not seeing the "JavaScript Error" you mentioned, in either popup or page modes. So I guess that might be related to your app somehow. See if you can duplicate that in any of the examples.
On the number front - what picture are you using for the number? I did some experimenting, and the short answer is that if you make a field a "number" then literally no formatting is allowed in some browsers.
Now the experience does change from one browser to the next, but it appears that "no formatting" is allowed in numbers used in a "number" field. The browser may format the number (or may not) - but the "value" of the number is a strict number.decimal with no other formatting (no commas, no spaces etc). If you need formatted numbers then you need to use a String field. (and yes, I understand what that means).
I will add some code to the 5.39 build (out later this week) which enforces the number picture on number fields - in the meantime you can change the picture on fields if you like, it needs to be in the form
@n_x.y
or
@n0x.y
where x and y are the only variables you can change.
if you use 0 instead of _, then the leading zeros are dropped in most browsers anyway.
Whichever one you pick, the number itself may, or may not, be formatted on the browser. For example, on chrome the number displays as
12345.67
with no formatting. On the iPad it displays as
12 345.67 (using an automatic space separator.)
You'd think the space separator is better, but it can be a problem - entering a number like a "year" renders as 2 011 which is a bit uncool.
In short, consider the number field to be "formatted" - or more accurately "formatted by the browser however it pleases".
cheers
Bruce
Topic: iPad with iOS5: Number Fields show empty data + "Error in site JavaScript" (Read 10071 times)