as far as opera is concerned I can say that it is related to if the plugin has focus or not. if the plugin doesn't have focus the click is getting through, if the plugin has focus they don't.
this results in a behaviour like this:
"first click works(1)" -> "subsequent clicks dont(2)" -> "click outside plugin(3)" -> repeat
My speculations about what happens:
(1): When you click on the plugin area the click gets registered by the browser which activates the plugin and forwards the click to it via the API.
(2): the clicks are directly handled by the plugin -> something bad is happening here
(3): when you click outside the plugin area you take away the focus from it and thus also rip it off the mouse/keyboard control -> subsequent clicks are again registered by the browser
As I said these are speculations as I don't have the slightest clue about how the plugin API really works, but it would explain the behavior that I see here.
as far as opera is concerned I can say that it is related to if the plugin has focus or not. if the plugin doesn't have focus the click is getting through, if the plugin has focus they don't.
this results in a behaviour like this:
"first click works(1)" -> "subsequent clicks dont(2)" -> "click outside plugin(3)" -> repeat
My speculations about what happens:
(1): When you click on the plugin area the click gets registered by the browser which activates the plugin and forwards the click to it via the API.
(2): the clicks are directly handled by the plugin -> something bad is happening here
(3): when you click outside the plugin area you take away the focus from it and thus also rip it off the mouse/keyboard control -> subsequent clicks are again registered by the browser
As I said these are speculations as I don't have the slightest clue about how the plugin API really works, but it would explain the behavior that I see here.