4 ms·

Not only date/datetime/time fields are broken. Also type=number does not work consistently across different locales and different browsers. Some don't let you t

by janci 10y ago

Not only date/datetime/time fields are broken. Also type=number does not work consistently across different locales and different browsers. Some don't let you type decimal comma.

adrianratnapala 10y ago
Is a "decimal comma" a thausands separator, or is it a decimal-point for locales where that is expressed by a comma?
- heinrich5991 10y ago
  It's the separator between the whole and fractional parts of the number.
- rhizome 10y ago
  I'm not sure this is universal, but locales which use a period for a thousands separator use a comma as a decimal point, and vice-versa.
  - m_t 10y ago
    It's not universal, that wouldn't be complicated enough!
edoceo 10y ago
IE doesn't understand max attribute. Sometimes marks an error with large (but inconsistent) value. Id est: use max="100000". Then on one IE/Edge 16000 is an error but 15000 is OK. Different IE/Edge box its 18000 cap. I have to make a custom UI component to make this work (riotjs)
freditup 10y ago
Also with type=number fields: some support showing a leading "0" while others don't. Seems like a small detail, but it all adds up to death by a thousand cuts and custom implementations of everything.
zbraniecki 10y ago
Hi, I'm one of the engineers working on date/time fields [0] (you can see the design document for them here[1]) for Firefox. We're on the way to support them and hopefully support them well. Now, I also happen to be working on refactor of our Intl code, so I should be able to help with the number field being inconsistent. If you can file a bug and prepare a minimized testcase, I'd be happy to fix it! :) [0] https://bugzilla.mozilla.org/show_bug.cgi?id=888320 https://bugzilla.mozilla.org/show_bug.cgi?id=888320 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1069609 https://bugzilla.mozilla.org/show_bug.cgi?id=1069609
- err4nt 10y ago
  Hey @zbraniecki, thanks for the work you're doing. I use type=number cautiously for self-built tools for my own use, but so far have avoided it in production code. Thanks to your effort maybe someday I'll be able to use this 'for real'!

by janci 10y ago

Not only date/datetime/time fields are broken. Also type=number does not work consistently across different locales and different browsers. Some don't let you type decimal comma.

adrianratnapala 10y ago

Is a "decimal comma" a thausands separator, or is it a decimal-point for locales where that is expressed by a comma?

heinrich5991 10y ago
It's the separator between the whole and fractional parts of the number.
rhizome 10y ago
I'm not sure this is universal, but locales which use a period for a thousands separator use a comma as a decimal point, and vice-versa.
- m_t 10y ago
  It's not universal, that wouldn't be complicated enough!

edoceo 10y ago

IE doesn't understand max attribute. Sometimes marks an error with large (but inconsistent) value. Id est: use max="100000". Then on one IE/Edge 16000 is an error but 15000 is OK. Different IE/Edge box its 18000 cap. I have to make a custom UI component to make this work (riotjs)

freditup 10y ago

Also with type=number fields: some support showing a leading "0" while others don't. Seems like a small detail, but it all adds up to death by a thousand cuts and custom implementations of everything.

zbraniecki 10y ago

Hi, I'm one of the engineers working on date/time fields [0] (you can see the design document for them here[1]) for Firefox. We're on the way to support them and hopefully support them well. Now, I also happen to be working on refactor of our Intl code, so I should be able to help with the number field being inconsistent. If you can file a bug and prepare a minimized testcase, I'd be happy to fix it! :) [0] https://bugzilla.mozilla.org/show_bug.cgi?id=888320 https://bugzilla.mozilla.org/show_bug.cgi?id=888320 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1069609 https://bugzilla.mozilla.org/show_bug.cgi?id=1069609

err4nt 10y ago
Hey @zbraniecki, thanks for the work you're doing. I use type=number cautiously for self-built tools for my own use, but so far have avoided it in production code. Thanks to your effort maybe someday I'll be able to use this 'for real'!