462099 - Focus not placed in Google's search field when page loaded in background tab

Status: RESOLVED WORKSFORME

(Camino Graveyard :: Tabbed Browsing, defect)

Description

[BuggyUK]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.4pre) Gecko/2008101818 Camino/2.0a1 (like Firefox/3.0.4pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.4pre) Gecko/2008101818 Camino/2.0a1 (like Firefox/3.0.4pre)

When I open a new tab, and then select Google, the cursor automatically goes to the entry box, so I can type immediately.

When I open a Google tab by command click, the cursor does not auto go to the entry box, and as I usually am typing my search head down, I do not notice that I am not entering any information into the google search box.

It is the same for other one entry boxes too from other sites.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Command click should place cursor into first entry box

Comment 1

[BuggyUK]

This only happens when links open in background in 2.01, when opened in forgound, it is OK

I find 1.6.4 Camino places cursor into first box even when opened in background

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Offhand, it sounds like this is more fallout from the key loop that should be fixed by bug 461403.

Can you check this later in the 20081029 nightly that will be available in a few hours and see if it works?

Comment 3

[philippe (part-time)]

That never worked with nightly builds from 2008 (and probably older), and doesn't work in a build with bug 461403 fixed.

Doesn't work in Minefield builds / Firefox3.0.3 either (nor Fx 2).

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This might be a security fix, then.  If someone has time to chase down when it stopped working, that would be useful.

Comment 5

[philippe (part-time)]

Old stuff:
2005101908 (1.0+) works
2005102008 (1.0+) fails

with 2 tests: 
1. cmd click on bookmark bar
2. cmd click on link to google

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-10-19+07%3A00%3A00&maxdate=2005-10-20+08%3A00%3A00&cvsroot=%2Fcvsroot

result of the camino part for bug 306245 ?

Comment 6

[Chris Lawson (gone)]

Mmm, yeah, I bet you're right.

Murph, when you get a chance, can you look at this?

Comment 7

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

OK, then it sounds like this is WONTFIX; it's the security fix I was thinking of (see bug 124750, mentioned in sfmr's checkin comment).

The fact that it went for three years on the branch without ever being fixed bothers me, though.

Comment 8

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #7)
> The fact that it went for three years on the branch without ever being fixed
> bothers me, though.

Oh, it was fixed on branch, then backed out on the branch because it caused bug 313811.

Have I mentioned I hate focus bugs?

Comment 9

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Or, this could be confirmed and made to depend on bug 307933 (via bug 303871).

We should also make sure that none of the testcases in bug 299677 show us exhibiting problematic behavior.

Comment 10

[Clint Priest]

This is still an issue with FireFox 3.5.5, should I re-post as a new bug with that product?

Comment 11

[Chris Lawson (gone)]

(In reply to comment #10)
> This is still an issue with FireFox 3.5.5, should I re-post as a new bug with
> that product?

This is a Camino bug, not a Firefox bug, so if you see a similar bug in Firefox, you should search for similar bugs in that component, as well as testing a recent nightly to see if the bug still occurs there, and if your search finds nothing and you still see the bug in a recent nightly, then yes, you should file a new bug in the Firefox component.

Comment 12

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

hendy says this is fixed in 1.9.2; we can mark it so if we get official 1.9.2 nightlies.

Comment 13

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #12)
> hendy says this is fixed in 1.9.2; we can mark it so if we get official 1.9.2
> nightlies.

So marking (well, WFM, because we have no idea what Gecko change fixed it).