-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Fix dir in Provider Context to prefer existing dir #35702
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?
Conversation
📊 Bundle size reportUnchanged fixtures
|
|
Pull request demo site: URL |
| @@ -0,0 +1,7 @@ | |||
| { | |||
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.
🕵🏾♀️ visual changes to review in the Visual Change Report
vr-tests-react-components/Avatar Converged 1 screenshots
| Image Name | Diff(in Pixels) | Image Type |
|---|---|---|
| vr-tests-react-components/Avatar Converged.badgeMask.normal.chromium.png | 5 | Changed |
vr-tests-react-components/Charts-DonutChart 1 screenshots
| Image Name | Diff(in Pixels) | Image Type |
|---|---|---|
| vr-tests-react-components/Charts-DonutChart.Dynamic.default.chromium.png | 5581 | Changed |
vr-tests-react-components/Positioning 1 screenshots
| Image Name | Diff(in Pixels) | Image Type |
|---|---|---|
| vr-tests-react-components/Positioning.Positioning end.updated 2 times.chromium.png | 33 | Changed |
vr-tests-react-components/TagPicker 1 screenshots
| Image Name | Diff(in Pixels) | Image Type |
|---|---|---|
| vr-tests-react-components/TagPicker.disabled - Dark Mode.disabled input hover.chromium.png | 658 | Changed |
There were 1 duplicate changes discarded. Check the build logs for more information.
layershifter
left a comment
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.
@anarmawala thx for contributing, however the current behavior is intentional as explicit is better over implicit.
For context, this also affects SSR scenarios as document is not available in Node env and the current PR will result in potentially different defaults on a client and a server.
|
I’m with @layershifter on this - it could lead to a hydration issue. If you want to reuse |

Please verify that:
masterbranchyarn changelocallyPrevious Behavior
The dir in ProviderContext automatically gets assumed to
ltr'.New Behavior
If we already had a direction specific on the html level then we should already take preference to that.
Related Issue(s)
The Provider Context now reads the
document.dirand if a value ofrtlorltrexists then use that, otherwise, assumeltr.