Closed
Bug 1278601
Opened 8 years ago
Closed 8 years ago
URL auto completion forgets port number
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 764062
People
(Reporter: ffux, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160503092831
Steps to reproduce:
go to a URL including a port number : eg localhost:631
open a new tab and start to type localhost
Actual results:
the dropdown list appears with the first entry : "Visit localhost/"
Expected results:
well if I need to specify a port number, it is not an optional extra. For this feature to be useful it needs to propose the URL complete with the port number I used when it was typed.
Can you please provide a testcase, a URL or more information so we can test this issue?
Also, can you please retest this using latest Firefox release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
Flags: needinfo?(ffux)
I already provided the test case. Assuming that CUPS is installed, port 631 will respond with the CUPS admin interface. It is a real example.
Our security policy does not allow installing unstable, non distro releases, you'll have to try typing localhost:631 yourself in whatever special conditions you consider appropriate. Please report back if you find something different to what I've reported.
Comment 3•8 years ago
|
||
The suggestion list shows the url but not the port number with it. still it shows the same url with same port.
But the question comes now is, 'what happens when there are same url and different port number?'
If we don't see the port number, we can't choose from the list which port we are gonna visit.
Component: Untriaged → Location Bar
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(ffux)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•