When I'm using the TAB applet doesn't get focus. See attached example
Comments
It works for IE already. Chrome uses the same plugin API as FireFox does - NP API . We haven't checked with Google yet but it doesn't look like they implemented this addition to NPAPI spec either. As I know they work on new plugin API - Pepper API.
02-07-2013
Is it possible to fix the problem in other browsers, like Google Chrome?
26-06-2013
The response from Mozilla was that they are not planning to implement Advanced Key Handling spec or any other new NPAPI features, since their NPAPI implementation is in maintenance-only mode.
26-06-2013
The main native plugin window don't get any message from FireFox or Chrome when user presses TAB key inside browser window and the next element which is expected to get focus is an applet. And it seems that this functionality is not implemented in FireFox and Chrome.
There is an issue https://bugzilla.mozilla.org/show_bug.cgi?id=93149 and it's not solved for more then 10 years. To address these kind of problems an NPAPI:AdvancedKeyHandling specification was developed but it seems not yet implemented (https://bugzilla.mozilla.org/show_bug.cgi?id=491141).
Besides W3C DOM limits limit the tabIndex property to the following element objects: <A>, <AREA>, <BUTTON>, <INPUT>, <OBJECT>, <SELECT>, <TEXTAREA> (http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#adef-tabindex). To this list, Interent Explorer adds <APPLET> and other element objects.
12-06-2013
Works only in IE, doesn't work in Firefox and Chrome. I tried tabIndex 0 and 1, both don't work
07-06-2013
Can you please try specifying the tabindex attribute of the applet tag? The attached sample (with the tabindex attribute) starts working to me - tested on Win7 + IE9.
06-06-2013
This bug is a blocker for the Uninstall Applet (UA) to be Accesible certified (actually the significant issue).
We would need to know if this could be addressed as part of 7u40 for the UA to be certified respectively.
05-06-2013
Not a P2 by ILW, should be a P4
09-04-2013
This issue is blocking the accessibility testing (keyboard only) of the uninstall applet, so increasing the priority