After setting the location bar to blank, leaving it should result in the current page identity information and address being restored in it

RESOLVED INACTIVE

Status

()

--
major
RESOLVED INACTIVE
11 years ago
6 months ago

People

(Reporter: adelfino, Unassigned)

Tracking

Trunk
Points:
---
Bug Flags:
blocking-firefox3 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008030506 Minefield/3.0b5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008030506 Minefield/3.0b5pre

After setting the location bar to blank, leaving it should result in the current page identity information, and address being restored in it.

Reproducible: Always

Steps to Reproduce:
1. Go to any page.
2. Clear the location bar.
3. Click anywhere else, for example, the content area.
Actual Results:  
No address, or identity information is known for the current page.

Expected Results:  
The identify information and address should be restored.
(Reporter)

Updated

11 years ago
Version: unspecified → Trunk
(Reporter)

Updated

11 years ago
Flags: blocking-firefox3?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-firefox3? → blocking-firefox3-

Comment 1

10 years ago
Do you see this with FF 3.5 beta? 
 http://www.mozilla.com/en-US/firefox/all-beta.html

what do you mean by identify information?
why do you expect the address to be restored?  did it do that in FF2?

Comment 2

2 years ago
I guess what is meant that "Show site information" gets disabled. This still happens with FF 50.1.0 (Arch Linux 64-bit)

I would personally not want the address to be restored automatically. Site information would be nice to have and maybe the address could be restored somehow through the (i) button.. might get too complicated, though and a niche use case.

Comment 3

6 months ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.