Closed Bug 337215 Opened 19 years ago Closed 14 years ago

Focus state of the search box should not be remembered per tab

Categories

(Firefox :: Search, defect)

Product:
Firefox
Component:
Search
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: ancestor.ak, Unassigned)

References

Details

Steps to reproduce: 1. Have two tabs open. 2. Focus the search box. 3. Switch to the other tab. --- search box looses focus 4. Switch back to the first tab. --- search box is focused Currently the search box (content, selected engine etc) is per-window not per-tab. If so, the focus should not be remembered per tab either. This is inconsistent, the search box should be made either completely per-window or completely per-tab. Cf. bug 248955.
Depends on: 337945
This issue apply to two things : - The search engine box - The search text box (Control+F) In my case. I also have a small issue with the search text box : I'm browsing through a page with many links with the text-searching box 1 - I type my keyword in the searchbox followed by return 2 - I middleClick on a link to open the link as a background tab 3 - then I type return to search next occurence But in this case, the link was focused by middleclicking and return opened the focused link. I think this behaviour changed from Firefox1.5. I never had this annoying behaviour before (annoying at last for me ;) ).
Personally I'd prefer it if the search box only stayed open / visible on the tab that it was activated. I.e. I have 3 tabs open and open the search function on tab 1. When I move to tabs 2 or 3 the chances are I will not be searching for things on there so the search box should not be shown unless I specifically press command+F. This is clearly personal preference though so perhaps if it could be edited through the normal settings page(s)? Apologies if this should have been opened as a new 'bug' but I think it fits in with this as the search bar should not be present in the other tabs regardless of focus!
Are we talking about the search box in the navigation toolbar or about the find toolbar which opens at the bottom of the browser window? It looks like things are mixed up here.
ah, i may have confused issues with my post! i had, perhaps wrongly, assumed we were referring to the one that opens at the bottom of the browser. i will start a new bug instead. sorry guys!! MaFt
Gavin, do you know about which search box the reporter is talking?
Why don't you just ask the reporter directly? :) I obviously meant the web search box on the navigation toolbar.
You never reported back since you have filed the bug. I thought you were gone. Sorry. It would be great if you could re-test with Firefox 3.5.3 and check if it works for you. Both the search bar and the find toolbar behave the same for me with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090907 Shiretoko/3.5.4pre (.NET CLR 3.5.30729) ID:20090907041431 Opening a new tab the focus is moved to the location bar while navigating through tabs with ctrl+(shift)+t leaves the focus in one of the input fields. So for both it remembers the focus state per tab.
(In reply to comment #7) > Opening a new tab the focus is moved to the location bar while navigating > through tabs with ctrl+(shift)+t leaves the focus in one of the input fields. > So for both it remembers the focus state per tab. Right, same here.
(In reply to comment #8) > (In reply to comment #7) > > Opening a new tab the focus is moved to the location bar while navigating > > through tabs with ctrl+(shift)+t leaves the focus in one of the input fields. > > So for both it remembers the focus state per tab. > > Right, same here. Dao, isn't that the desired behavior? I think so but cannot find a bug right now which explains it.
WORKSFORME Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9pre) Gecko/20110103 Firefox-4.0/4.0b9pre Iceweasel 3.6.13 Focus no longer stays in search when switching tabs.
Indeed, thanks.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.