Bug Description
When writing a chat message that mixes an LTR language (like Russian or English) with an RTL word (like Persian or Arabic) in the same line, the text rendering breaks. After typing the RTL word, the rest of the sentence jumps to the wrong side and the entire sequence becomes reversed or misordered.
This is a bidirectional (BiDi) text issue.
Example in Russian + Persian:
"Я люблю سلام как дела"
→ After "سلام", the rest ("как дела") appears on the wrong side.
Steps to Reproduce
- Open any chat in Extera.
- Type an LTR sentence (e.g., in Russian or English).
- Insert an RTL word (e.g., Persian "سلام" or Arabic "كتاب") in the middle.
- Continue typing LTR after that word.
- Observe the broken reordering.
Expected Behavior
The sentence should display naturally with proper BiDi support: RTL text flows right-to-left, LTR text flows left-to-right, without breaking the word order (just like in Telegram, WhatsApp, or any properly implemented chat).
App Version
26.2.9
Additional Platform Information
Device: Android
Additional Context
This is likely caused by missing Unicode control characters (LRM/RLM) or incorrect textDirection / layoutDirection settings on the message input or message bubble views.
I can provide a screen recording if needed.
Bug Description
When writing a chat message that mixes an LTR language (like Russian or English) with an RTL word (like Persian or Arabic) in the same line, the text rendering breaks. After typing the RTL word, the rest of the sentence jumps to the wrong side and the entire sequence becomes reversed or misordered.
This is a bidirectional (BiDi) text issue.
Example in Russian + Persian:
"Я люблю سلام как дела"
→ After "سلام", the rest ("как дела") appears on the wrong side.
Steps to Reproduce
Expected Behavior
The sentence should display naturally with proper BiDi support: RTL text flows right-to-left, LTR text flows left-to-right, without breaking the word order (just like in Telegram, WhatsApp, or any properly implemented chat).
App Version
26.2.9
Additional Platform Information
Device: Android
Additional Context
This is likely caused by missing Unicode control characters (LRM/RLM) or incorrect textDirection / layoutDirection settings on the message input or message bubble views.
I can provide a screen recording if needed.