As far as I can tell from several years of following this bug, the problem is that The Powers That Be at MoCo have failed to come to a decision as to what, exactly, the "right" behaviour is.
It's not at all clear that https://wiki.mozilla.org/Plugins:AdvancedKeyHandling , linked in comment 269, is still the current plan, and it's VERY clear that such a plan does _absolutely nothing_ to address existing versions of plug-ins. I do not believe -- and most of the saner commenters here seem to agree -- that a solution requiring third-party vendors to release new versions of their plug-ins is a viable one. The fix needs to be made in Gecko itself. The problem is convincing Firefox drivers that this "advanced key handling" spec is a non-starter.
As far as I can tell from several years of following this bug, the problem is that The Powers That Be at MoCo have failed to come to a decision as to what, exactly, the "right" behaviour is.
It's not at all clear that https:/ /wiki.mozilla. org/Plugins: AdvancedKeyHand ling , linked in comment 269, is still the current plan, and it's VERY clear that such a plan does _absolutely nothing_ to address existing versions of plug-ins. I do not believe -- and most of the saner commenters here seem to agree -- that a solution requiring third-party vendors to release new versions of their plug-ins is a viable one. The fix needs to be made in Gecko itself. The problem is convincing Firefox drivers that this "advanced key handling" spec is a non-starter.