Just ran into a real bummer resulting from the disparity in how various browsers handle HTML5. I have a grid displayed on a mobile device with two fields containing currency values. I used a numeric HTML5 tag to get the mobile device to pop up the appropriate numeric keyboard. I also used a predefined currency display format. Everything was working fine until I discovered that in browsers other than Firefox the contents of the currency fields are not displayed! As it turns out, Firefox is apparently the only browser that correctly handles this situation. I personally confirmed that IE 10 and Safari do not display the fields. Alpha technical support also confirmed that Chrome does not display the fields.
Per Jerry Brightbill at Alpha, �We have been researching the problem, and the primary cause is the way browsers deal with HTML formatting. The issue is that IE and other browsers say that a number MUST be a number - i.e. no characters other than 0-9 and "." - meaning that if you try to set it with a "string value" such as "$5.00" it will just null it out. They don't even accept a thousands separator. For some reason, Firefox is the exception. If you remove the dollar sign prefix and any thousands separator, everything works.�
Based on Jerry�s description of the issue, I suspect this problem occurs in UX components as well as grids, although I have not tested it. Also, there ay be similar issues with other HTML5 field types and field formatting.
So, I found myself having to choose between a nicely formatted currency field or a more efficient mobile user experience in which the appropriate keyboard appears. My real concern is that there are other undiscovered differences between the various browsers, which means it is probably good practice to test using every browser that may be used to access your system. I really love this �standard� HTML.
Terry
Per Jerry Brightbill at Alpha, �We have been researching the problem, and the primary cause is the way browsers deal with HTML formatting. The issue is that IE and other browsers say that a number MUST be a number - i.e. no characters other than 0-9 and "." - meaning that if you try to set it with a "string value" such as "$5.00" it will just null it out. They don't even accept a thousands separator. For some reason, Firefox is the exception. If you remove the dollar sign prefix and any thousands separator, everything works.�
Based on Jerry�s description of the issue, I suspect this problem occurs in UX components as well as grids, although I have not tested it. Also, there ay be similar issues with other HTML5 field types and field formatting.
So, I found myself having to choose between a nicely formatted currency field or a more efficient mobile user experience in which the appropriate keyboard appears. My real concern is that there are other undiscovered differences between the various browsers, which means it is probably good practice to test using every browser that may be used to access your system. I really love this �standard� HTML.
Terry
Comment