45692 - WebTextField Type Number Cannot Set with Commas

Targets Web
1

I just submitted a Web Bug report: <https://xojo.com/issue/45692> - WebTextField Type Number Cannot Set with Commas

Example Project: CampSoftware - Developer of Custom Database Driven Apps

Steps: - Drag a WebTextField to a WebPage.

  • Set the WebTextField Type to Number.
  • Set the WebTextField Text to a number with a comma in it like “1,000”.
  • Result is nothing in the WebTextField

Expected Result:
See a number with a comma in the WebTextField.

Actual Result:
The WebTextField shows nothing.

Workarounds:
Stop using commas.

2

What browser are you using? The input type="number" has different effects on different browsers.

For example, I’m using Safari. If I type a comma in manually, the stepper doesn’t recognize the field as a number anymore and will start it at 0 again. However, when testing on Firefox it recognizes the number and takes out the comma.

It may not be a Xojo issue, or one they can fix.

Your workaround seems accurate for now.

3

Good idea Tim. I tested with Safari. I just tried Chrome and Firefox with the same result as Safari.

4

I believe in a type number with locale US, comma is not considered a valid character. You should instead consider entry with only 1234567890. and format the number with the thousand separators in lostfocus.

5

Interestingly, I can type 1,000 and exit the field.

But NumbertTypeTextField.Text = “1,000” results in nothing in the field.

6

[quote=295682:@Hal Gumbert]Interestingly, I can type 1,000 and exit the field.

But NumbertTypeTextField.Text = “1,000” results in nothing in the field.[/quote]
To see how the browser handles that value, try to change it with the stepper.
As noted, Safari throws your value out, Firefox removes the comma, and Chrome is not welcome on my machine.

7

Chrome - the all consuming beast

8

In Chrome, a number field does not accept comma. I would tend to believe the solution is to use JavaScript to obtain the same result in all browsers.