In Firefox, you can type letters and symbols (for example abc or @#$) into a Number field in a Glide form, but Glide won’t accept them as a value. This is how Firefox handles number fields. Your data isn’t affected.
What you’ll see
Browser | What happens when you type letters or symbols in a Number field |
Chrome, Edge, Brave, Arc, Opera (Chromium-based) | The characters are blocked and nothing appears in the field. |
Firefox | The characters appear in the field, but they aren’t accepted as a value. |
In Firefox, this can look like:
The field shows text such as
asdf@#%.If the field is Required, the Submit button stays disabled.
No error message appears next to the field.
Why this happens
Glide uses the browser’s built-in number input for Number fields. Each browser decides what you can type into that input:
Chromium-based browsers stop invalid characters as you type them.
Firefox lets you type any character but marks the input as invalid. It then reports the field to the app as empty.
Because Firefox reports the field as empty, Glide treats it as empty.
Is my data affected?
No. Invalid text in a Number field is never saved to your data source. A form can’t submit invalid text from a Number field.
Note: if a valid number is followed by an invalid character (for example 1990x), Firefox reports the whole field as empty. If the field is optional, the form can be submitted with that field blank, even though 1990x is still visible on screen.
What to do
In Firefox: enter only digits (plus a decimal point or minus sign if needed). If Submit stays disabled, check your Number fields for stray letters or symbols and remove them.
For the most consistent experience: use a Chromium-based browser such as Chrome or Edge, which blocks invalid characters automatically.
For important numeric fields: consider marking them Required. Then a field that Firefox reports as empty will block submission instead of being saved blank.