275895 - Keyboard shortcuts ignored when mouse pointer is positioned over flash content

Status: VERIFIED DUPLICATE of bug 78414

(Firefox :: Keyboard Navigation, defect)

Description

[bonjour]

When the mouse pointer is positioned over flash content on a web page the event
handling is probably delegated to the flash plugin and as a result keyboard
shortcuts and mouse scroll wheel actions are ignored. It's better to fix the
problem as the user, depending on the position of the pointer, may be lead to
think that the browser is disfunctioning.

Comment 1

[Chris Blore]

As far as I can see, it depends on having clicked over the area covered by the
flash content before shortcuts become unresponsive. When I directly visit a site
and try to use keyboard shortcuts, it works fine.

Otherwise, confirmed under Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8a6) Gecko/20041221 Firefox/1.0+ 

Comment 2

[Jesse Ruderman]

Which keyboard shortcuts work and don't work when your mouse pointer is over 
Flash?  (Arrow keys?  Ctrl+N?)

This could be a dup of bug 95541 or bug 78414.

Comment 3

[Chris Blore]

It appears to be a dupe of bug 78414 

Comment 4

[bonjour]

Sorry my bug report is a duplicate. Surprisingly those other bugs are so old
that I faild to find them before reporting mine. How come nobody has ever cared
to fix them after some 3 years time?!
 @Jesse: all the keyboard shortcuts like ctrl+t, alt (for menu navigation),
ctrl+n are disabled when mouse is over flash content. This is the "lost focus"
problem reported elsewhere.

Comment 5

[Jesse Ruderman]

I'm not convinced that this is a dup of bug 78414.  Why would putting the mouse
cursor over Flash cause it to get focus?

> How come nobody has ever cared to fix them after some 3 years time?!

Probably because the bug is very hard to fix.

Comment 6

[Aaron Leventhal]

Putting the mouse over the Flash content causes bug 78414 when "sloppy focus" is
used. Often a setting used on Linux. I've seen another dupe like this before.

Believe it or not, a fix is being worked on, albeit slowly. First the API has to
be agreed on. Several companies are working together on this and it will make it
into the next gen plugin API. Be patient.

Comment 7

[Jesse Ruderman]

Thanks Aaron.

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