Add getOwnerDocument and getOwnerWindow utils and fix usePress

[slye-stripe]

This PR adds the getOwnerDocument and getOwnerWindow util function in @react-aria/utils. It then uses it in usePress.ts as a test and adds a corresponding test in usePress.test.js.

This is a follow-up to #5070, which involves incremental changes.

Related to #4634

✅ 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:

🧢 Your Project:

Stripe - Connect Embedded Components

[slye-stripe]

Choosing to warn here instead of error and only applying to @react-aria/interactions for now, will only switch to error once we have rolled out all the fixes.

[snowystinger]

couple quick things, thanks for turning on the lint rule and the test, those will be a big help

[snowystinger]

I am not sure this test is helping, if I revert your changes, this one still passes. This is surprising to me. Do you know why that would be?

also, the click event is still fired in the non-virtual case as well, see https://codesandbox.io/s/musing-aryabhata-nhlwyf?file=/src/App.js to see what events the browser fires

I do love adding a test for virtual cursors in addition to pointer. We'll also need one for keyboard I think. Or if it's left off intentionally, that'd be good to know.

[slye-stripe]

I believe it's because there's no listener for the click event but only an onClick handler function so that is always fired since we target the element.

I'll add a test for the keyboard event.

[slye-stripe]

@snowystinger Added the test for keyboard event, hoping this is correct?

[snowystinger]

Sorry, I don't see the keyboard event test. Just remember, the tests you add will help us to not break your code in the future. So even if you've traced the events and have determined you only need to fireEvent with a couple of them, it's better to fire as many as is reasonable. We may change the internals of usePress in the future and depend on those events. We'll try our best to point out those cases where it's better to add an extra seemingly unneeded event.

[slye-stripe]

Apologies, added them, lmk if there are other events I should be adding!

[snowystinger]

GET_BUILD

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-17
• View the storybook-16
• View the documentation

[rspbot]

## API Changes

unknown top level export { type: 'identifier', name: 'Column' }
unknown top level export { type: 'identifier', name: 'Column' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }
unknown type { type: 'link' }

@react-aria/utils

useFormReset

-
+getOwnerDocument {
+  el: Element | null
+  returnVal: undefined
+}

getOwnerDocument

-
+getOwnerWindow {
+  el: Element | null
+  returnVal: undefined
+}

---

[snowystinger]

thank you for your patience and thanks for getting this started.