Open
Bug 152148
Opened 23 years ago
Updated 3 years ago
LTR text incorrectly appears as RTL (inlines with dir="ltr" on Visual Hebrew pages)
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
REOPENED
People
(Reporter: xslf, Unassigned)
References
()
Details
(Keywords: rtl)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
BuildID: 20022053012 (moz 1.0)
The attached page was created using word, with a mess of CSS. All the english
text in the page appears as RTL, althugh it has <span dir=ltr> wrapping it.
For some reason, attempting to create a simplified text case does give the full
results- so I suspect that something in the interaction of that full page is
giving use this mess
Reproducible: Always
Steps to Reproduce:
1. go to above url
Actual Results: the english text appear reversed
Expected Results: should display ok
it is difficult to create a simplified test case for this page, since view
source opens inside mozilla (which is not easy to work with for editing text) on
one hand (bug 35268 and bug 35268) and copy/paste is dificult since I am unable
to select multiple lines (bug 82352 ).
Once those two bugs would be fixed, it will make it *much* easier to isolate
bugs like on this page.
Comment 1•23 years ago
|
||
WFM Win2k 20020614 trunk
I see the main text going RTL and all the embedded English text going LTR.
Updated•23 years ago
|
Summary: LTR text incorrectly sppears as RTL → LTR text incorrectly appears as RTL
Comment 2•23 years ago
|
||
There is no charset declared in the page. If you select ISO-8859-8 (manually or
as default charset) it displays as Shosh describes. If you select ISO-8859-8-I
it displays correctly.
| Reporter | ||
Comment 3•23 years ago
|
||
Did some more testing:
It seems like whenthe browser default is set to visual Hebrew, and a Hebrew page
has no charset declaration, Roman text is displayed RTL.
I am getting this with build 2002061603 on OSX as well.
Simple example:
* set your default charset to visual Hebrew.
* Go to this page:
http://bugzilla.mozilla.org/attachment.cgi?id=46897&action=view
See the English text appear as RTL.
OS: Windows 98 → All
Hardware: PC → All
Comment 4•23 years ago
|
||
I think this is INVALID. Visual means "no reordering". If dir=ltr, then
everything is left-to-right, including Hebrew; if dir=rtl, then everything is
right-to-left, including ENGLISH.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 5•23 years ago
|
||
The original page i filed the bug against is actully logical- but missing a
charset declaration, so it was using my deafult (visual). However, the Hebrew
parts are sorrunded with dir=rtl, and the english parts with dir=ltr.
When using my default, the dir=ltr got ingnored.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 6•23 years ago
|
||
Now I get it. You expect that inline elements in a visual page should change
direction according to the dir attribute.
The team at IBM who implemented Bidi considered this and decided that on visual
pages the dir attribute would only take effect at the block level - e.g. you
could have two paragraphs in different directions by using <p dir="rtl"> and <p
dir="ltr"> - but not at the inline level.
Is there an example of a real-world visual page which will break with our
current behaviour? If the problem only arises in artificial circumstances and
can be corrected by changing encoding (or changing from viusal to logical when
we have a UI to do so), then this is still INVALID, or at least WONTFIX.
| Reporter | ||
Comment 7•21 years ago
|
||
*** Bug 222606 has been marked as a duplicate of this bug. ***
Comment 8•20 years ago
|
||
(In reply to comment #6)
> Is there an example of a real-world visual page which will break with our
> current behaviour? If the problem only arises in artificial circumstances and
> can be corrected by changing encoding (or changing from viusal to logical when
> we have a UI to do so), then this is still INVALID, or at least WONTFIX.
http://www.cameri.co.il/mg/tickets.asp (second line)
QA Contact: zach → bugs.mano
Comment 9•20 years ago
|
||
Not seeing any English text reversed at http://www.avi.org.il/ ...
Updated•19 years ago
|
Summary: LTR text incorrectly appears as RTL → LTR text incorrectly appears as RTL (inlines with dir="ltr" on Visual Hebrew pages)
Comment 11•17 years ago
|
||
Mass-assigning the new rtl keyword to RTL-related (see bug 349193).
Keywords: rtl
Comment 12•17 years ago
|
||
In Firefox 2.0.0.15 on Windows and Linux, I am seeing ltr content being reversed in text areas and in source code after Hebrew characters.
This doesn't seem to happen with Arabic characters.
Comment 13•17 years ago
|
||
I can't seem to reproduce that. Can you point to a specific site where you are seeing it?
Comment 14•17 years ago
|
||
(In reply to comment #13)
> I can't seem to reproduce that. Can you point to a specific site where you are
> seeing it?
>
It might be related to a special character?
The source of this document http://nzfusion.com/james/hebrew_firefox.html appears the same in Gedit, which I used to create the document.
Comment 15•17 years ago
|
||
You're right about the special character. The line <h3>בית</h3> has a U+202E RIGHT-TO-LEFT OVERRIDE character at the beginning of the Hebrew text (I've addded a U+202C POP DIRECTIONAL FORMAT after it when pasting into here, otherwise all of this comment would be oot sdrawkcab)
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: mano → layout.fonts-and-text
Updated•14 years ago
|
Assignee: mozilla → nobody
Comment 16•12 years ago
|
||
I'm wondering if this is the bug being hit by the project at https://github.com/lwt-project/lwt which is using LTR mixed with RTL in modified overlib ( http://www.bosrup.com/web/overlib/ ) tooltips.
Is a U+202E RIGHT-TO-LEFT OVERRIDE character involved in stopping the ▶ line from being LTR? Screenshot of the problem:
http://imgh.us/RTL-in-tooltip.png
which should look like:
http://lwt.sourceforge.net/img/26.jpg
(because of either old js or the Learning with Texts project uses textareas in frames the tooltips may not always appear if you're testing)
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•