OS: Windows 11
Browser: Chrome (official version) and Edge (for testing the fix)
Web Clipper version: 1.6.1
Obsidian version: 1.12.7
Describe the bug
I have encountered a significant rendering issue when using the extension to read or clip content that mixes Arabic and English. When an English word or technical term appears within an Arabic sentence, the punctuation and parentheses become scrambled or reversed.
Additionally, the text visually clips against the edges of the popup container. I have compared the official Chrome version (where the text is broken) with a local build I am testing on Edge (where I have applied a fix). The difference is quite clear: the current official version struggles with bidirectional (BiDi) isolation in the popup fields.
Expected behavior
I expected the text fields to handle mixed-script content gracefully. The alignment should remain consistent, and punctuation should stay in its logical place without any text being cut off by the container boundaries.
URLs where the bug occurs
This occurs on any page where the content or note properties contain both RTL (Arabic) and LTR (English) text.
Your template file
Using the default template.
Additional context:
I have already investigated the root cause and identified that the popup fields lack proper bidirectional isolation. I have successfully tested a fix locally by implementing dir="auto" and unicode-bidi: plaintext across the relevant styles and templates.
I will open a PR shortly that includes the fix for these issues. I have screenshots ready to attach to this thread to show the "before and after" results from my testing.
before
after
OS: Windows 11
Browser: Chrome (official version) and Edge (for testing the fix)
Web Clipper version: 1.6.1
Obsidian version: 1.12.7
Describe the bug
I have encountered a significant rendering issue when using the extension to read or clip content that mixes Arabic and English. When an English word or technical term appears within an Arabic sentence, the punctuation and parentheses become scrambled or reversed.
Additionally, the text visually clips against the edges of the popup container. I have compared the official Chrome version (where the text is broken) with a local build I am testing on Edge (where I have applied a fix). The difference is quite clear: the current official version struggles with bidirectional (BiDi) isolation in the popup fields.
Expected behavior
I expected the text fields to handle mixed-script content gracefully. The alignment should remain consistent, and punctuation should stay in its logical place without any text being cut off by the container boundaries.
URLs where the bug occurs
This occurs on any page where the content or note properties contain both RTL (Arabic) and LTR (English) text.
Your template file
Using the default template.
Additional context:
I have already investigated the root cause and identified that the popup fields lack proper bidirectional isolation. I have successfully tested a fix locally by implementing dir="auto" and unicode-bidi: plaintext across the relevant styles and templates.
I will open a PR shortly that includes the fix for these issues. I have screenshots ready to attach to this thread to show the "before and after" results from my testing.
before
after