Bug 1756160 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Thanks for the bug report!

This is essentially a version of bug 1398528, which is unfortunately non-trivial to fix in general (see bug 1398528 comment 3 and 4; the spec doesn't dictate exact behavior here, and Safari continues to match our behavior, and fully-correct blocking is non-trivial due to localization complexity).

In the meantime, see bug 1398528 comment 26 for a sort-of workaround; you can use JavaScript or CSS to detect the fact that the number field contains an invalid number.

--> Marking as duplicate of bug 1398528
Revision 1 by
on 
Thanks for the bug report!

This is essentially a version of bug 1398528, which is unfortunately non-trivial to fix in general (see bug 1398528 comment 3 and 4; the spec doesn't dictate exact behavior here, and Safari continues to match our behavior, and fully-correct blocking is non-trivial due to localization complexity).

In the meantime, see bug 1398528 comment 26 for a sort-of workaround; you can use JavaScript or CSS to detect the fact that the number field contains an invalid number (and alert the user to that fact so that they can edit or reenter it).

--> Marking as duplicate of bug 1398528

Back to Bug 1756160 Comment 2