Closed Bug 688108 Opened 14 years ago Closed 14 years ago

Ellipsis appears at front of text when nesting direction ltr inside a rtl

Categories

(Core :: Layout: Text and Fonts, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: anthonygerrard+bugzilla.mozilla.org, Unassigned)

Details

Attachments

(1 file, 1 obsolete file)

Attached file direction-bug.html (obsolete) —
User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Build ID: 20110902133214 Steps to reproduce: Nest a ltr anchor inside a rtl div and include an ellipsis in the text: "Find out more…" Test case attached. I'm using Firefox 6.0.2 on Windows 64 bit professional Actual results: You get "…Find out more" Expected results: "Find out more…"
Attachment #561406 - Attachment mime type: text/plain → text/html
The ellipsis character is created using UTF-8 encoded special character. UTF-8 mode was set using initial sequence inside the file in the original testcase. Updated testcase has UTF-8 specified via meta tag.
Attachment #561406 - Attachment is obsolete: true
I can confirm the problem on Win XP too and on today's Nightly 9.
Status: UNCONFIRMED → NEW
Component: General → Layout: Text
Ever confirmed: true
OS: Windows Vista → Windows XP
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Hardware: x86_64 → x86
Version: 6 Branch → Trunk
Does this look different in other browsers? I believe that our rendering is correct here, because the CSS direction property on its own doesn't affect the reordering of text in inline elements. To get "Find out more…", use either <a style="direction: ltr; unicode-bidi: embed"> or preferably just <a dir="ltr">
http://www.w3.org/TR/css3-writing-modes/#direction : "The ‘direction’ property has no effect on bidi reordering when specified on inline elements whose ‘unicode-bidi’ property's value is ‘normal’. " This one?
Yes, exactly.
The rendering here is the same in Gecko, WebKit, and Presto, as expected. I haven't tested Trident, but I would be _very_ surprised if they get this wrong. As far as I can tell, this bug is invalid....
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
IE8 renders it the same as Firefox (ellipsis on the left).
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: