329527 - Tabs loaded in background don't always get keyboard focus when previous tab closed

Status: VERIFIED DUPLICATE of bug 280390

(Camino Graveyard :: Tabbed Browsing, defect)

Description

[mark dalrymple]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/417.9 (KHTML, like Gecko) Safari/417.8
Build Identifier: 2006021400 (1.0)

His Highness Pinkerton has witnessed this one.  If you load some pages in background tabs, and then start closing tabs, newly displayed tabs don't have keyboard focus, so space-bar paging won't work

Reproducible: Always

Steps to Reproduce:
1. goto http://vagilemind.com/clanlord
2. cmd-click a topic
3. close the tab, then command-click a bunch of threads
4. now close a tab (cmd-w) and then press space.  the space doesn't page the page
Actual Results:  
space doesn't page the resulting page

Expected Results:  
space should page the page

Comment 1

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

Can we figure out when this regressed?  I wonder if it's one of smfr's -getFrontmostWindow changes or the fix for that bug where the pointer wouldn't change to a hand on 10.4?

Comment 2

[Chris Lawson (gone)]

Is this for sure a regression? I'm not having any luck reproducing, although I know something similar to this was discussed on the MZ forums and possibly here on bugzilla several months back.

Smokey, were you able to repro?

cl

Comment 3

[mark dalrymple]

Pink had some problems confirming it on an IRC channel today.  If you go to the URL listed, command-tab a bunch of forums, then command-tab a bunch of discussion threads, then the forums will happily page with the space bar, but the discussion threads won't - almost like something is stealing focus.  For comparison, Safari and Firefox both page the discussion threads

Comment 4

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

I see this issue from time to time, but I've never paid close attention to when or what might cause it.

We did some further investigation tonight and this seems to be a dupe of bug 280390, or the issue behind bug 280390...once Chris was using a profile that started showing ads, he could repro.

*** This bug has been marked as a duplicate of 280390 ***

Comment 5

[Samuel Sidler (old account; do not CC)]

Nice catch.