Skip to content

Conversation

@plesiecki
Copy link

@plesiecki plesiecki commented Oct 31, 2025

Closes #9122

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

Could run the test from here https://github.com/plesiecki/react-spectrum-releasePointerCapture-repro

🧢 Your Project:

@plesiecki
Copy link
Author

I have signed the CLA

@snowystinger
Copy link
Member

closing to refresh cla check

@snowystinger snowystinger reopened this Nov 3, 2025
Copy link
Member

@snowystinger snowystinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure the check for has/releasePointerCapture is needed anymore
https://developer.mozilla.org/en-US/docs/Web/API/Element/releasePointerCapture#browser_compatibility
Question to the team, shall we get rid of that? we mock it in jsdom where it doesn't exist yet

If you're firing the events, then, to be most accurate, you need to set the pointer capture just before pointer down. https://www.w3.org/TR/pointerevents2/#implicit-pointer-capture this happens implicitly for touch screens.

This may also be reconsidered whenever we try to fix #8249 as I think it's related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DOMException: Element.releasePointerCapture: Invalid pointer id

2 participants