Skip to content
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

Value auto for dir probably shouldn't say "no explicit directionality" #1079

Open
aphillips opened this issue May 15, 2023 · 0 comments · May be fixed by #1118
Open

Value auto for dir probably shouldn't say "no explicit directionality" #1079

aphillips opened this issue May 15, 2023 · 0 comments · May be fixed by #1118
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@aphillips
Copy link

dir member
https://w3c.github.io/manifest/#dir-member

"auto" (default)
No explicit directionality.

The value auto isn't exactly the same as "no explicit directionality". It means that the direction of strings with this value should be estimated using the first-strong part of the bidi algorithm. It is an explicit value. It also implies that the value should be bidi isolated when displayed. Perhaps say "Direction determined from content" instead?

Note that content which fools the "first-strong" detection in auto is common: an actual direction value such as rtl or ltr is preferred to just relying on auto.

Note that there was some previous discussion of this topic in #926

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant