Daniel Ruf

It affects pickadate and other things too.

Also see https://github.com/amsul/pickadate.js/issues/1138 https://github.com/amsul/pickadate.js/pull/1140 https://github.com/amsul/pickadate.js/pull/1145 Again, this is not a bug on our side as the code worked like thjs the whole time and still works in all other browsers....

See https://github.com/Dogfalo/materialize/blob/v0.100.2/js/forms.js

> Chrome 73 removed that behavior to match the FF implementation. Unfortunately at the same time FF also switch to Chrome behavior to get more consistency but this behavior is...

> http://archives.materializecss.com/0.100.2/forms.html#select It happens in 0.100.x. See https://github.com/Dogfalo/materialize/issues/6312 https://github.com/Dogfalo/materialize/issues/6316 https://github.com/Dogfalo/materialize/issues/6318 https://github.com/Dogfalo/materialize/issues/6320 https://github.com/Dogfalo/materialize/issues/6323 > Go to the docs : http://archives.materializecss.com/0.100.2/forms.html with Chrome On Select section and try to the first select....

You can see the unminified code at https://github.com/Dogfalo/materialize/blob/v0.100.2/js/forms.js

This does not fix most cases, see https://codepen.io/DanielRuf/pen/rRENBm?editors=1010 and the two lines with `// this will not work` as this is still a regression bug in Chromium.

Maybe but let's get back to the root cause. A change in Chromium. It worked the last 3-5 years. So it is still a regression on your side as this...

As previous contributor and maintainer of both projects I never saw such an issue in the last years - in any of the big browsers - until the change in...

https://github.com/amsul/pickadate.js/pull/1145#issuecomment-479532964 might give an idea.