Closed
Bug 390549
Opened 17 years ago
Closed 17 years ago
IPv6 addresses in URLs have [] disappear in non-editing location bar state
Categories
(Firefox :: Address Bar, defect)
Firefox
Address Bar
Tracking
()
VERIFIED
FIXED
Firefox 3 alpha8
People
(Reporter: dbaron, Assigned: dao)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
3.22 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
In the non-editing state of the location bar, the "[" and "]" that go around an IPv6 address in a URL disappear. Steps to reproduce: 1. go to http://[2001:200:0:8002:203:47ff:fea5:3085]/ (that's the current IPv6 address of http://www.kame.net/) 2. look at the location bar Expected results: Location bar shows http://[2001:200:0:8002:203:47ff:fea5:3085]/ (whether editing it or not) Actual results: Location bar shows http://[2001:200:0:8002:203:47ff:fea5:3085]/ (unless you edit it) Tested in a Firefox trunk debug build on Linux pulled at 2007-07-31T14:00-07:00
Flags: blocking-firefox3?
Assignee | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
OS: Linux → All
Hardware: PC → All
Assignee | ||
Comment 1•17 years ago
|
||
Assignee: nobody → dao
Attachment #275305 -
Flags: review?(gavin.sharp)
Updated•17 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Updated•17 years ago
|
Flags: in-litmus?
Updated•17 years ago
|
Target Milestone: --- → Firefox 3 M9
Updated•17 years ago
|
Attachment #275305 -
Flags: review?(gavin.sharp) → review+
Updated•17 years ago
|
Keywords: checkin-needed
Target Milestone: Firefox 3 M9 → Firefox 3 M8
Comment 2•17 years ago
|
||
Checking in urlbarBindings.xml; /cvsroot/mozilla/browser/base/content/urlbarBindings.xml,v <-- urlbarBindings.xml new revision: 1.17; previous revision: 1.16 done
Comment 3•17 years ago
|
||
I've added https://litmus.mozilla.org/show_test.cgi?id=5019 to verify the address's integrity. While I'm here, verifying that we don't truncate the URL in any way, using today's trunk builds.
Status: RESOLVED → VERIFIED
Flags: in-litmus? → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•