You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, MedusaJS Admin does not dynamically set the dir attribute on the <html> tag based on the locale's direction (RTL or LTR). This can lead to accessibility and usability issues for users in RTL locales (e.g., Arabic). Additionally, styles like border-r on the MainSidebar are not dynamically adjusted for RTL locales, resulting in inconsistent UI experiences.
Proposed Solution
Set Default dir Value
Use the default language's rtl property to set the initial dir attribute on the <html> tag during app initialization.
Update dir Dynamically
Use a useEffect hook in the i18n-provider to update the dir attribute whenever the language changes.
Dynamic Styles
Ensure styles like border-r or border-l are dynamically adjusted based on the dir attribute.
Why is this Important?
Accessibility: Proper text direction is crucial for RTL languages to ensure readability and usability.
Consistency: Ensures the UI behaves consistently across all locales.
The text was updated successfully, but these errors were encountered:
Problem
Currently, MedusaJS Admin does not dynamically set the
dir
attribute on the<html>
tag based on the locale's direction (RTL or LTR). This can lead to accessibility and usability issues for users in RTL locales (e.g., Arabic). Additionally, styles likeborder-r
on theMainSidebar
are not dynamically adjusted for RTL locales, resulting in inconsistent UI experiences.Proposed Solution
Set Default
dir
ValueUse the default language's
rtl
property to set the initialdir
attribute on the<html>
tag during app initialization.Update
dir
DynamicallyUse a
useEffect
hook in thei18n-provider
to update thedir
attribute whenever the language changes.Dynamic Styles
Ensure styles like
border-r
orborder-l
are dynamically adjusted based on thedir
attribute.Why is this Important?
The text was updated successfully, but these errors were encountered: