We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
useButton and all react-aria button instances should be able to disable preventDefault.:
const ref = useRef<HTMLButtonElement | null>(null); const { buttonProps } = useButton(props, ref); const { children } = props; const onPointerDown = (e: any) => { buttonProps.onPointerDown?.({ ...e, preventDefault: () => {}, stopPropagation: () => {}, }); }; return ( <button {...buttonProps} onPointerDown={onPointerDown} ref={ref}> {children} </butt
Currently librabries can't detect outside click if react-aria button clicked
provide props to prevent this behaviour
Floating ui doesn't get outside click and doesn't close popover. (And i would not want to use overlay, because i need scroll events also)
No response
The text was updated successfully, but these errors were encountered:
As of the latest release, usePress no longer calls preventDefault. See https://react-spectrum.adobe.com/releases/2025-03-05.html#usepress-update. Are you using the latest version?
Sorry, something went wrong.
No branches or pull requests
Provide a general summary of the feature here
useButton and all react-aria button instances should be able to disable preventDefault.:
Now i need to hack like this:
🤔 Expected Behavior?
😯 Current Behavior
Currently librabries can't detect outside click if react-aria button clicked
💁 Possible Solution
provide props to prevent this behaviour
🔦 Context
Floating ui doesn't get outside click and doesn't close popover. (And i would not want to use overlay, because i need scroll events also)
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: