Closed Bug 899429 Opened 11 years ago Closed 11 years ago

entire address location does not show on url bar

Categories

(Firefox :: Address Bar, defect)

22 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 667178

People

(Reporter: illumilore, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130627185035

Steps to reproduce:

to reproduce I went to http://google.com


Actual results:

in the location bar, only "www.google.com/" was shown.



Expected results:

The whole "http://www.google.com/" should be shown, rather than only part of the address.
This is correct by design. If you want to see the full address, you can go to about:config and change browser.urlbar.trimURLs to false.
Trimmed URL, nothing new or buggy.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
But then why does it not hide the url if it says https://? That is inconsistent to hide one but not the other.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Only HTTP is trimmed, HTTPS is not due to security reasons for the user.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → INVALID
Component: Untriaged → Location Bar
Resolution: INVALID → DUPLICATE
That still doesn't answer the question of why it is being trimmed in the first place. If the https is shown for security reasons, then wouldn't you want the user to know when they are NOT on a secure page by showing the http?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Because by default, the protocol is HTTP and it's unsecure, so it's redundant to display it. Secure pages are identified with the padlock, see https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure

Other protocols are displayed normally.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → DUPLICATE
Because a bigger difference (the lack of https where it should be) is easier to notice.
You need to log in before you can comment on or make changes to this bug.