This bug is intended to track outstanding issues with implementing the Navigator
4.x plugin API. It is *not* intended for general "legacy plugin X doesn't work"
Please see bug 35682, 56464, bug 56650, bug 57499. Track-worthy?
None of those appear to be pointing to specific issues with the 4.x plugin API.
You're right about 57499. I've no idea why I thought otherwise before. Sorry.
over to av to see if he wants to use this tracking bug...
marek/jud, is this on anyone's requirement list?
I don't see known customers requesting it. Jud?
depends on what our plugin story is. if it is "we don't support 4.x plugins, and
all plugin vendors must rewrite their plugins to our new api" then this bug
isn't needed. This will boil down to how many plugin vendors we can get to convert.
Moving to m1.0.
Arun, here's another meta bug you may want to keep track of for outstanding 4xp
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1
(you can query for this string to delete spam or retrieve the list of bugs I've
setting to 1.1 with the dependent bugs
setting to PL2:P1
batch: adding topembed per Gecko2 document
Bulk adding topembed keyword. Gecko/embedding needed.
moving to 1.4 beta, dependent bugs will be worked on in plug-in branch
I think we can consider this resolved fixed given that our NPAPI plugin implementation has been mature for a while now.