Closed Bug 613129 Opened 14 years ago Closed 14 years ago

autocomplete window stays visible when user action causes different content/tab/window

Categories

(Camino Graveyard :: Location Bar & Autocomplete, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 309370

People

(Reporter: lthompson.22, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.13pre) Gecko/20101114 Camino/2.1a1pre (like Firefox/3.6.13pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.13pre) Gecko/20101114 Camino/2.1a1pre (like Firefox/3.6.13pre)

Another "this doesn't seem right to me, but what do I know...". I tried to look at as many auto.?complete bugs as seemed relevant, so sorry if I missed a dupe somehow.

STR
1. Command-L and type something so the auto-complete window comes up
2. change your mind and decide to close the tab with Command-W

AR: The previous tab comes to front with the new text and cursor still in the location bar and the auto-complete box still showing.

ER: The previous tab comes to front with the URL of that tab's actual page in the location bar, focus is on the page content not the location bar, and the auto-complete box has gone away.

These AR/ER also apply when other actions are taken, via menu or keyboard, such that new content is loaded in the current tab, eg. Back or Forward, though Cmd-B, Cmd-Y, and Cmd-<number> seem to work properly; a different tab becomes current, eg. Close/Previous/Next Tab; a different window comes to the front, eg. Downloads or Preferences; or even when Camino gets put in the background altogether, eg. click on the Desktop or a different app in the Dock. The auto-complete box also stays visible when an Open/Save dialog is invoked, which seems odd.

Safari has what seems to me the more logical behavior here, with the auto-complete box disappearing on any kind of context change. Chrome and Firefox 4 do too, for the most part, though there are inconsistencies; Firefox 3.6 is even more inconsistent.

Camino 2.1a1pre, but I think most of this applies to Camino 2.0 as well. Tested only in 10.6.


Reproducible: Always
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.