Closed
Bug 1510434
Opened 6 years ago
Closed 6 years ago
[RTL] URL loses the domain highlight after switching from a New Tab to any other tab
Categories
(Firefox :: Address Bar, defect)
Firefox
Address Bar
Tracking
()
RESOLVED
FIXED
Firefox 65
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox63 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | --- | fixed |
People
(Reporter: itiel_yn8, Assigned: yehudab)
References
Details
(Keywords: regression, rtl, Whiteboard: fixed by backout)
Attachments
(1 file)
262.00 KB,
image/gif
|
Details |
This is a regression from bug 1503161. STR: 1. Change Nightly's UI to RTL (set intl.uidirection to 1 in about:config) and restart Nightly 2. Open 2 New Tabs 3. In the second tab open any URL and let it finish loading 4. Go to the first tab (which should still be the New Tab) 5. Go back to the second tab. AR: The second tab's domain part of the URL is not hightlighted, and the entire URL is in the same color. ER: Hightlight the domain. See attached. Not sure if this is considered a security issue.
Updated•6 years ago
|
status-firefox63:
--- → unaffected
status-firefox64:
--- → unaffected
status-firefox65:
--- → affected
status-firefox-esr60:
--- → unaffected
Comment 1•6 years ago
|
||
Off-hand, I don't understand how a rule specific to the placeholder-shown case could cause an issue like this, as it shouldn't apply to the case where the tab has content loaded, with a URL. Perhaps the logic in https://searchfox.org/mozilla-central/source/browser/components/urlbar/UrlbarValueFormatter.jsm#69 isn't being run at the right time, or something? Dão, can you take a look?
Flags: needinfo?(dao+bmo)
Comment 2•6 years ago
|
||
I've backed out bug 1503161.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(dao+bmo)
Resolution: --- → FIXED
Whiteboard: fixed by backout
Updated•6 years ago
|
Updated•6 years ago
|
Assignee: nobody → yehudab
Target Milestone: --- → Firefox 65
Updated•5 years ago
|
Group: firefox-core-security → core-security-release
Updated•5 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•