Closed
Bug 1442711
Opened 7 years ago
Closed 7 years ago
Field of input type=text dir=rtl text selection is incorrect for bidi text
Categories
(Core :: DOM: Selection, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 312678
People
(Reporter: addison, Unassigned)
Details
(Keywords: rtl)
Attachments
(1 file)
47.58 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20180118122319
Steps to reproduce:
This was discussed on the winter list starting here here: https://lists.w3.org/Archives/Public/www-international/2018JanMar/0104.html
1. Create an input field of type=text with dir=rtl.
2. Set the value of the field to "abcdאבגדהוזתefgh" (abcdאבגדהוזתefgh)
3. Place the cursor at either end of the text (click in and press Home or End)
4. Shift-arrow across the text (or use the mouse to perform text selection)
Actual results:
The text does not select properly according to the Unicode bidi algorithm. Directional runs can be selected, but the entire text cannot be highlighted. Crossing RTL/LTR boundaries is incorrect. Note that a field with dir=ltr works correctly!
Expected results:
Correct selection. I have attached a screen shot of some screenshots of both FF and the equivalent (proper) behavior in Chrome.
Comment 1•7 years ago
|
||
Can you help with triaging this Kato-san? I'm not sure if it is layout or Internationalization and if we have it filed already.
Flags: needinfo?(m_kato)
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Has Regression Range: --- → irrelevant
Has STR: --- → yes
Closed: 7 years ago
Component: Untriaged → Selection
Keywords: rtl
Product: Firefox → Core
Resolution: --- → DUPLICATE
Comment 3•7 years ago
|
||
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #1)
> Can you help with triaging this Kato-san? I'm not sure if it is layout or
> Internationalization and if we have it filed already.
Although it is DOM's selection API issue, I think that nsFrameSelection should consider this situation...
Flags: needinfo?(m_kato)
You need to log in
before you can comment on or make changes to this bug.
Description
•