159896 - 'Clear Location Bar' button is not clearing the location bar

Status: VERIFIED WORKSFORME

(SeaMonkey :: Preferences, defect)

Description

[Ian McCall]

'Clear Location Bar' button is not clearing the location bar.

Can't post a URL to demonstrate of course, but if I type
"http://www.eruvia..org" (extra '.' deliberate), it goes into the location bar
history. I don't want it there, so I go to preference and click 'Clear Location
Bar' - back to the location bar and all of my previous locations are still there
(including the incorrrect ..org one).

Browser string for my version is: Mozilla/5.0 (Windows; U; WinNT4.0; en-US;
rv:1.0.0) Gecko/20020530

Comment 1

[Ian McCall]

More information. A bit of research shows that the problem only occurs if
multiple browser tabs are open.

Behaviour:

If a single browser window is open:
Going to preferences and select 'Clear Location Bar' works exactly as expected.
When quitting Mozilla, the cleared location bar is finalised and on opening
Mozilla for a second time the bar remains clear.

If multiple tabs are open:
Going to preferences and selecting 'Clear Location Bar' clears the bar for the
currently active tab, but leaves all others intact. When quitting Mozilla, the
location bar must be updated from the non-active tabs, since when restarting
Mozilla the location bar contains all the values it used to have before being
cleared.


Hope this helps.

Comment 2

[R.K.Aa.]

Unable to reproduce on a day old CVS build, Linux:
Clearing the location bar clears it for all tabs: when hitting the arrow to the
right of URL dropdown, all tabs dropdowns turned out to be empty.

Comment 3

[R.K.Aa.]

..and after quitting and restarting mozilla, the dropdown was still empty.

Comment 4

[Ian McCall]

Downloaded and retested against 1.1b on NT4 - Mozilla/5.0 (Windows; U; WinNT4.0;
en-US; rv:1.1b) Gecko/20020721

Problem not seen in this version - maybe fixed since the 1.0 I was originally
reporting against?

Comment 5

[Wesha]

Ian: most likely. The bug reports are most useful when the version they are
reported against is not older than 2 weeks. Otherwise, the odds that the bug is
gone are great.

==> WORKSFORME.
Reasons: 1) unable to reproduce bug
         2) Reporter unable to reproduce bug on a recent build (as per comment 4)

Comment 6

[sairuh (rarely reading bugmail)]

mass-verifying WorksForMe bugs.

reopen only if this bug is still a problem with a *recent trunk build*.

mail search string for bugspam: AchilleaMillefolium