Eric van der Vlist

As a workaround you can use the NativeSelect element I don't see it in the suid documentation but it's implemented (see https://github.com/swordev/suid/tree/main/packages/material/src/NativeSelect).

@FezVrasta you're not limited to strings and you can include HTML fragments and React components. Your file will need to be a .jsx (or tsx) and you'll be able to...

That's not in the documentation but it's mentioned in issue (#115), however, doing more tests it seems to be working fine with Chrome but not with Firefox where is raises...

In fact that doesn't work with Chrome either (the only reason it didn't raise the error was because it was set with th edefault language while Firefox was not). The...

There doesn't seem to be a way to differentiate between simple and complex objects in JavaScript, however, React components have a $$typeof property which will likely not appear on "simple"...

I have open [an issue in localized-strings](https://github.com/stefalda/localized-strings/issues/31).

This workaround doesn't work with suid/material 0.9.1and raises an error (TypeError: Cannot set property type of # which has only a getter) at InputBase.jsx:310.

Commenting lines 309 to 315 fixes this error but will probably have side effects !

In fact the issue is that HTMLTextAreaElement has a type property (with "textarea" has a value) and this type property is read only while HTMLInputElement has a read/write type property....

A workaround could be to use a date or datetime-local type: However when I try to use it in my application, I get an error because the InputBase components uses...