kevinmitch14
kevinmitch14
I think this has been fixed, #3001
Working for me, it's best to create a reproduction of the issue.
It's because you are setting the value to "". It's selecting option1 as a result and not triggered the native required. `const [value, setValue] = React.useState("");` For example if you...
I'm not too sure why having value={""} would result in "option1" being the active value though. Maybe it's a bug, I'm not too sure. If you think it is, maybe...
Not sure if related but I also get some weird behaviour when using `panelBackground="translucent"` https://github.com/user-attachments/assets/6612dad5-a2a5-4a75-a2f9-ce84ee12a0e0
What version are you using? The `loading` prop was introduced in v3. The best thing to do is to provide a small reproduction.
It would be nice to know if `GenericServerException`, `OauthException` etc. can be 'leaked' to the client
I mean is it safe to expose these on the client!
Hmm, this still runs into the issue where if you define `maxWidth={"200px"}` and the trigger is 300px wide, the `Popover.Content` will be 300px 🤔
This is basically a mirror of #369