[Select] Set the onChange's event.target.value

[michaldudak]

As noted in mui/material-ui#34408 (comment), it's worth ensuring that the event object in Unstyled Select's onChange method has a target property with a valid value property.

[harsh5902]

shall i work on this issue?

[michaldudak]

Sure, go ahead!

[jesrodri]

@harsh5902 are you still working on this? if not, can I take it?

[harsh5902]

yes i am still working on it.

[michaldudak]

I have investigated the problem in more depth. In the case of Select, setting the event.target.value may not work the best because:

• HTMLSelectElement.value is defined as a string. In our case, this could be any object.
• In the case of select multiple, the value contains only the first selected element. The whole collection is available under the selectedOptions, which is a set of HTMLOptionElement instances. This is not available in the case of our custom Select.

I'd like to wait and see if this becomes a problem in real-world applications. When we see concrete examples of how this should work, we may be able to think of the right solution. Until then, I'm putting it on hold.

A side note: neither Headless UI nor Radix UI provides the event object in their selects' change handlers.

[Sen-442b]

@michaldudak slightly unrelated, but is there a similar rationale behind not supporting e.target.name as well?

[michaldudak]

We are considering changing this API in the new version of the Select but nothing is set in stone yet.