Continuing the discussion from What does the support mixed text direction setting do?:
Should we deprecate this setting, composer button and add dir="auto"
by default in our text areas? IE is not a blocker anymore.
Continuing the discussion from What does the support mixed text direction setting do?:
Should we deprecate this setting, composer button and add dir="auto"
by default in our text areas? IE is not a blocker anymore.
This setting also affects non-textarea things. e.g. it is used to apply dir=
to paragraphs/quotes in posts:
And topic titles:
and more.
Can we use dir="auto"
for all these things now?
Makes sense, users need this everywhere they input text:
I took a stab at updating our support_mixed_text_direction
setting to lean on dir="auto"
instead of using a regex to parse all user input at render-time:
I think weâll need to keep this. Setting dir="auto"
on a textarea will use a heuristic to decide the direction of the entire textarea. That doesnât sound too useful if youâre writing a post which contains a combination of rtl and ltr languages. So I think the button is required for you to switch back & forth while editing?
In cooked posts, the dir="auto"
can be applied per-paragraph, which solves that problem.
Would be great if some readers / writers of RTL languages can weigh in on that, and perhaps take a look at the PR. (cc @osama - git suggests you have done a lot of work on our RTL logic)
Yes, exactly, the button is very useful when youâre typing a post that mixes RTL and LTR languages.
Your PR LGTM @david
This is now merged. Please let us know if you have any feedback
This topic was automatically closed after 171 days. New replies are no longer allowed.