Open Bug 814030 Opened 8 years ago Updated 6 years ago
FF17 shows RTL text of browser title
Steps to reproduce: (1) Load the URL into the web browser. (2) Observe the titlebar. Expected: The characters " - Mozilla Firefox" Actual: These characters are actually reversed.
The view-source rendering is also slightly different than what shows up in the tab's title.
(In reply to Alex Vincent [:WeirdAl] from comment #0) > Steps to reproduce: > (1) Load the URL into the web browser. > (2) Observe the titlebar. > > Expected: The characters " - Mozilla Firefox" > Actual: These characters are actually reversed. I'm unable to reproduce this given these steps. Is there something that's missing? (i.e did you perhaps set an RTL preference in about:config?)
(In reply to Scott Johnson (:jwir3) from comment #3) > I'm unable to reproduce this given these steps. Is there something that's > missing? (i.e did you perhaps set an RTL preference in about:config?) Not to my knowledge - I tried it using a fairly clean - if old - profile on Linux and now on Windows.
OS: Linux → All
There's a U+202E (right-to-left override, RLO) character in the page's <title>, before the characters "LTR", and there's no matching PDF (pop directional formatting); i.e., the title is actually "xkcd: <RLO>LTR". So when " - Mozilla Firefox" is appended to the title, the RLO is still in effect, and those characters also take on RTL directionality.
In the tab title I see "xkcd: LTR", but in the tooltip when hovering the tab title I see "xkcd: RTL".
(In reply to Scott Johnson (:jwir3) from comment #2) > The xkcd comic is not a valid testcase. ;) *sigh* Sorry, my bad. I was sleeping when I wrote this.
View-source is also affected: I see <title>xkcd: </title>RTL This may be bug 717811.
This bug also affects Ubuntu. Screenshot at http://shkspr.mobi/blog/wp-content/uploads/2014/02/Firefox-RTL-Search-fs8.png A Google / Bing / Yahoo search like https://www.google.co.uk/search?q=Harry+%E2%80%AErettoP will reverse the text of the Window - due to the presence of ‮ in the <title>.
You need to log in before you can comment on or make changes to this bug.