-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
[Select] Implement pointer cancellation #45789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[Select] Implement pointer cancellation #45789
Conversation
cbb9faa
to
74a4a03
Compare
Netlify deploy previewhttps://deploy-preview-45789--material-ui.netlify.app/ Bundle size report
|
5d7bc9c
to
eb21c2d
Compare
eb21c2d
to
aeab281
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Kartik-Murthy Thanks for the PR! Let’s keep it focused on one thing. Issues #44505 and #45374 shouldn’t be addressed yet — they’ll be handled once the Material UI Select is built on top of Base UI. For now, let’s just implement #45301. Could you remove the other changes and add a test case for #45301?
Thank you @ZeeshanTamboli for the guidance! I've revised the PR to focus solely on fixing issue #45301 . I've removed the changes related to the other issues as requested and added test cases to verify the behavior. Let me know if you'd like to see any additional changes. |
863f35e
to
7a58f33
Compare
7a58f33
to
5a7a06a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before reviewing this in detail, I’m wondering whether we should even add this feature (or maybe it's an accessibility bug?), given that it already works in Base UI Select — and Material UI will eventually be built on top of Base UI.
@aarongarciah @DiegoAndai What do you think? How far off is the Material UI release based on Base UI? How should we handle support requests and community PRs like this in the meantime? There have been a few similar feature additions — see #45789 (review).
If we decide to go ahead with adding this in 7.x
despite the upcoming Base UI integration in a new major version, I’ll proceed with a full review.
369791d
to
74f06a8
Compare
- Restore original import order as per project conventions
74f06a8
to
d91d5ba
Compare
Hey @Kartik-Murthy, thanks for working on this, sorry for the delay. @ZeeshanTamboli, we can move forward with this review. I don't have an estimate for Material UI being rebuilt on top of Base UI. About the solution, I wonder if there's a way of handling the mouse up from the items, instead of having to set a global event listener. Did you explore that idea? |
@DiegoAndai I’ve moved the pointer cancellation logic into the |
@@ -571,6 +602,7 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) { | |||
...listProps, | |||
}, | |||
paper: { | |||
ref: paperRef, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A ref could be comming in paperProps
that breaks this, doesn't it? We should probably merge paperRef
, paperProps.ref
, and pass that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch. Handled this.
I agree, it's also how Base UI does it 👍🏼: https://github.com/mui/base-ui/blob/master/packages/react/src/select/trigger/SelectTrigger.tsx#L161 |
@ZeeshanTamboli good work, this looks almost ready for me. I'm only missing the selection when onMouseUp happens on a select item. I think we should add this, following Base's implementation which adds it to the items onMouseUp handler: https://github.com/mui/base-ui/blob/master/packages/react/src/select/item/SelectItem.tsx#L182 Would that be possible? This is what I'm referencing, selecting with a single click: Screen.Recording.2025-07-04.at.15.32.11.mov |
@DiegoAndai Do you consider this to be part of the pointer cancellation feature we are doing in this PR? If not, we can handle it in a separate PR. |
Yes, to me the "mouse down > mouse up" flow is not complete without item selection. I would rather merge all at once. |
@DiegoAndai Done. Ready for further review. |
Code looks good @ZeeshanTamboli! Multiple select demos are broken though: https://deploy-preview-45789--material-ui.netlify.app/material-ui/react-select/#multiple-select Base UI recently implemented multiple, maybe there are some clues there? mui/base-ui#2173 Scary that these weren't caught by tests, lets add some after finding the root cause of why this PR broke the demos. |
@DiegoAndai Fixed now. It was occuring because both the
I think the bug wasn't caught because the tests didn't simulate both |
Thanks @ZeeshanTamboli!
Could we use cc @siriwatknp for awareness. We're close to merging this. May I ask you to review it? I want to be extra cautious with the |
Description
This PR resolves pointer cancellation issues in the Select component to ensure compliance with WCAG 2.5.2 accessibility requirements.
Changes
Fixes #45301
Aditional