Closed
Bug 277701
Opened 20 years ago
Closed 16 years ago
Wrong (bidi) caret symbol in URL bar after visiting RTL page
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
FIXED
People
(Reporter: MatsPalmgren_bugz, Assigned: smontagu)
References
(Blocks 1 open bug, )
Details
(Keywords: rtl)
Wrong caret symbol in URL bar after visiting RTL page.
STEPS TO REPRODUCE:
1. load http://www.mozilla.org.il/ (notice caret in URL bar is LTR)
2. create a new tab and load http://www.mozilla.org/
3. go back the the first tab
4. click on some links in the page until you get a RTL caret in the URL bar
(usually after just a few clicks)
5. go to tab 2 - notice that caret is still RTL
6. close the first tab
7. Notice that caret is still RTL
8. Visit a new page, e.g. http://www.google.com - caret is still RTL
EXPECTED RESULTS:
The caret symbol should not be the one used in RTL pages when the visited page
is LTR. (Should it ever be RTL in the URL bar in an en-US build?)
PLATFORMS & BUILDS TESTED:
Bug occurs in Mozilla 2005-01-06-05 trunk Linux.
Bug occurs in Firefox 1.0 trunk Linux.
ADDITIONAL INFORMATION:
It seems that the bug only occurs when using more than one tab.
Assignee | ||
Comment 1•20 years ago
|
||
(In reply to comment #0)
>(Should it ever be RTL in the URL bar in an en-US build?)
Yes, for example when entering a URI like http://he.wikipedia.org/wiki/מוזילה
I've never seen an RTL caret just from clicking on links (at least in builds
from the last year, since bug 162242 was fixed) and would like more exact steps
to reproduce. Is the bug Linux-specific?
Assignee | ||
Comment 2•20 years ago
|
||
Sorry, the URI in the previous comment was intended to be
http://he.wikipedia.org/wiki/מוזילה
Updated•20 years ago
|
Assignee: nobody → smontagu
Component: Layout → Internationalization
QA Contact: layout → amyy
Comment 3•19 years ago
|
||
> I've never seen an RTL caret just from clicking on links (at least in builds
> from the last year, since bug 162242 was fixed) and would like more exact steps
> to reproduce. Is the bug Linux-specific?
I have seen this same behavoir on Windows XP Firefox 1.5 and Windows XP Firefox 1.0.7:
The exact steps decribed above demonstate this bug. for example:
1) Open a tab to www.google.co.il
2) Type something into the search box
3) Press enter to get search results
4) Go back to an existing tab (not wwww.google.co.il) or create a new tab to an arbitrary address (say www.mozilla.org)
5) Notice, the caret symbol is still the RTL caret symbol. It will remain so until the session ends.
Expected results: When RTL page is left (ie, www.google.co.il), the default language chosen's (ie, en-us in my case) caret is used.
Comment 4•19 years ago
|
||
This might be related (or not), but go to the w3 home page (http://www.w3.org/), View Page Source and you will have a rtl cursor in the view source window. Or at least I do.
Also on any page where direction:rtl is specified (via css) for an object, all textboxes on the page are rendered with an rtl cursor including those which do not exist within the rtl object. That-is, the rtl property is affecting the cursor shape for every object on the page not just the object(s) matching the CSS selector rule.
Assignee | ||
Comment 5•19 years ago
|
||
All/All based on comments, but I still can't reproduce.
OS: Linux → All
Hardware: PC → All
Comment 6•19 years ago
|
||
*** Bug 312859 has been marked as a duplicate of this bug. ***
Comment 7•19 years ago
|
||
*** Bug 335831 has been marked as a duplicate of this bug. ***
Updated•18 years ago
|
Summary: Wrong caret symbol in URL bar after visiting RTL page → Wrong (bidi) caret symbol in URL bar after visiting RTL page
Comment 8•18 years ago
|
||
I didn't get what the platform is. On Linux, you shouldn't have such problems with Mozilla-1.8.1 / Firefox-2.0RC1.
Comment 9•17 years ago
|
||
Mass-assigning the new rtl keyword to RTL-related (see bug 349193).
Keywords: rtl
Assignee | ||
Comment 10•16 years ago
|
||
Fixed by bug 418513.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•