User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051806 Firefox Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051806 Firefox When I try to remove a line in the location bar, using the "delete" button on my keyboard, it actually removes TWO lines, but if I type again the url in the location bar, the second line which has disappear is still here ... Reproducible: Always Steps to Reproduce: 1. Go to a website you never had been before, well just try my blog : www.betaphile.net 2. Click on a few links inside the website 3. Then, type "betaph" in the location bar 4. Delete the first line you have Actual Results: It deletes TWO lines. Expected Results: It shoud deletes only one line.
I was about to fill a new bug report but this report is closely related to the bug I want to report. I am running Ubuntu 8.04 Hardy Heron amd64, with Firefox RC1 (firefox-3.0~rc1+nobinonly-0ubuntu0.8.04.1) First, I confirm the bug: I can reproduce it (notice that it is on a different OS). Second, I want to complement the description of the bug: "when you remove a entry, the address in the location bar is not updated". Steps to reproduce: 1. type anything in the location bar: the list pops up. 2. press the down arrow key once to select the first entry: the address in the location bar is updated. 3. press the "delete" key: the entry is removed, the previous second entry becomes the first one and is selected BUT the location bar still displays the address of the removed entry. Expected Result: 3. the location bar should display the address of the currently selected entry in the list after a remove. In the "Steps to reproduce" described by Kevin, at step 4, notice that the address in the location bar is still the one that has been removed (along with two entries removed) even if the first entry is selected.
Bulk closing all UNCONFIRMED bugs dealing with places that haven't had any bug activity in over 120 days, have no votes, and are not enhancement requests. If you are still experiencing this issue in Firefox 3.0 or later, please re-open the bug with steps to reproduce (if they were not part of the original comment).