Uh oh!
There was an error while loading. Please reload this page.
[react-interactions] Remove deprecated Scope APIs + update Focus components - #17859
Conversation
f0c9bac to
05a92b9CompareThis pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit f0c9bac:
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit cb9da2a:
|
Details of bundled changes.Comparing: b6173e6...cb9da2a react-test-renderer
react-native-renderer
react-art
react-dom
react-reconciler
ReactDOM: size: 0.0%, gzip: -0.0% Size changes (experimental) |
Details of bundled changes.Comparing: b6173e6...cb9da2a react-native-renderer
react-reconciler
react-dom
react-art
react-test-renderer
ReactDOM: size: 0.0%, gzip: -0.0% Size changes (stable) |
05a92b9 to
05ea82dCompare…onents/docs Remove Update tests
05ea82d to
cb9da2aCompare
About a year later, I'd like to ask if there's any plan or progress to bring these back. |
This PR removes the deprecated Scope APIs that handled traversal. These APIs are no longer used internally, and instead now use React Context and the
scope.getChildContextValues()API exclusively.Unfortunately, I've decided to also remove the
accessibilitydirectory from the React repository for now, which includes the accessibility components. Many of the tests/docs/components were out of date compared to their latest versions, which were migrated to our internal FB repository last year. Keeping the components in sync proved to be very time-consuming because of several differences. Notably, our internal Jest tests for these components made usage of our internal testing infrastructure which is not available in open-source right now, plus there were usages of other bits of Facebook IP that I'd have to remove before syncing back over.A more effecient long-term strategy will be to work with the partner teams involved and come up with a plan that involves moving these components back into open-source, probably under a different repository maybe, or maybe a different project relating to Facebook's accessibility work.