759089 - New tab : Firefox abandons the focus to the plugin and then fails to process key (!) commands

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Nicolas Barbulesco]

Hello,

Win XP, Firefox 11.

See also bug 735113, bug 380637, bug 78414.

I create a new Firefox window. I go to www.perdu.com . I create a second tab. I go to www.ratp.fr/informer/picts/plans/pdf/bus_banlieue/300/h_395.pdf . Firefox loads the PDF document, I look at it, but *I don't click in it*. *I don't even put my mouse over it*, *I don't scroll in it*. Then, I decide I don't want this PDF document anymore. Then, two cases, 1/ or 2/ :

1/ I decide to close the tab. I press Crtl W. I expect Firefox to close the tab at once. Instead, the tab becomes white, the PDF doc is gone, but the tab is still there. Really awkward. I press Ctrl W again, and now Firefox closes my tab.

2/ I decide to go somewhere else. I press Ctrl L. I expect Firefox to bring me in the location bar and to select the Web address so that I type another address. Instead, the Adobe Acrobat PDF plugin switches the PDF doc in a full view mode, without the toolbars. And I can press again Ctrl L, even ten times : the Adobe PDF plugin switches the PDF doc between its full view mode and its normal mode, but Firefox does not bring me in the location bar.

Ctrl L, Ctrl W are key (!) commands. In these cases, Firefox fails to process these commands, and the results are really awkward.

There are two parts in the problem :

A/ Firefox fails to process these commands when the plugin has the focus. This is bug 78414.

B/ As soon as Firefox loads the requested document, Firefox abandons the focus to the plugin.

My request :

As long as Firefox keeps having the behaviour A/, please correct the behaviour B/. When Firefox just loads the requested document, keep the focus in Firefox. And we can reasonably agree that the user clicks in the PDF doc if s/he wants to direct special keystrokes toward it.
I think we can apply that as well to other kinds of plugin contents, Flash for instance.

Thanks.

Nicolas

Comment 1

[Mats Palmgren (inactive)]

We're in the process of removing support for plugins (bug 1677160), so I think this bug is irrelevant now.