Closed Bug 482121 Opened 15 years ago Closed 15 years ago

While in a tab that is using the adobe reader plugin the firefox shortcuts are not functioning (for instance the new tab shortcut)

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 78414

People

(Reporter: zarzirim, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729)

Load firefox and navigate to some pdf document. Notice that the adobe plugin is activated like it should. Now while in the aforementioned tab try to use one of the Firefox KB shortcuts (For example: the new tab- ctrl+'T'). The shortcut is not working.

Now navigate open a new tab and navigate to any website and try the shortcut again--> working!

Select the "adobe" tab again and get the same result- KB shortcuts are not working. Select the regular website again and KB shortcuts are working.

This might be as specified by the developers but if in deed this is the case i think it will still be nice to have the ability to work with the firefox shortcuts (Maybe add a user preference about this).

Reproducible: Always

Steps to Reproduce:
1.Launch Firefox and navigate one tab to a regular website and the other to a pdf 
  document (the adobe plugin should kick in of course).
2.try the FireFox KB shortcuts in the "adobe" tab----> Not working.
3.try the KB shortcuts in the other tab----> working
Actual Results:  
As it says above- this is not a crash or anything like that- just less comfortable to me.

Expected Results:  
I wanted to have the Firefox KB shortcuts at all time or at least the ability to control whether they are active at all time or not.

Have a preference about it.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.