[META] Navigator 4.x plugin API implementation

RESOLVED FIXED in mozilla1.4beta

Status

()

Core
Plug-ins
P1
normal
RESOLVED FIXED
17 years ago
6 years ago

People

(Reporter: Braden, Unassigned)

Tracking

({meta})

Trunk
mozilla1.4beta
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PL2:P1])

(Reporter)

Updated

17 years ago
Keywords: 4xp
(Reporter)

Description

17 years ago
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"
reports.
(Reporter)

Updated

17 years ago
Component: Tracking → Plug-ins
Keywords: meta

Comment 1

17 years ago
Please see bug 35682, 56464, bug 56650, bug 57499. Track-worthy?
(Reporter)

Comment 2

17 years ago
None of those appear to be pointing to specific issues with the 4.x plugin API.
(Reporter)

Comment 3

17 years ago
You're right about 57499. I've no idea why I thought otherwise before. Sorry.
Depends on: 56311, 56584, 57499, 58491
(Reporter)

Updated

17 years ago
Depends on: 66205

Updated

17 years ago
Status: NEW → ASSIGNED

Comment 4

17 years ago
over to av to see if he wants to use this tracking bug...
marek/jud, is this on anyone's requirement list?
Assignee: chofmann → av
Status: ASSIGNED → NEW

Comment 5

17 years ago
I don't see known customers requesting it. Jud?

Comment 6

17 years ago
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.

Comment 7

17 years ago
Moving to m1.0.
Target Milestone: --- → mozilla1.0

Comment 8

16 years ago
Arun, here's another meta bug you may want to keep track of for outstanding 4xp 
isues.
Summary: Navigator 4.x plugin API implementation → [META] Navigator 4.x plugin API implementation
(Reporter)

Updated

16 years ago
Depends on: 105417

Comment 9

16 years ago
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 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
(Reporter)

Updated

16 years ago
Depends on: 98641, 117766
(Reporter)

Updated

16 years ago
Depends on: 115891

Comment 10

15 years ago
setting to 1.1 with the dependent bugs
Target Milestone: mozilla1.0.1 → mozilla1.1alpha

Comment 11

15 years ago
setting to PL2:P1
Severity: normal → critical
Priority: P3 → P2
Whiteboard: [PL2:P1]
Target Milestone: mozilla1.1alpha → mozilla1.0.3

Updated

15 years ago
Target Milestone: mozilla1.0.3 → mozilla1.1alpha

Updated

15 years ago
Severity: critical → normal

Updated

15 years ago
Priority: P2 → P1

Updated

15 years ago
Target Milestone: mozilla1.1alpha → mozilla1.2beta

Updated

15 years ago
QA Contact: chofmann → shrir

Comment 12

15 years ago
batch: adding topembed per Gecko2 document
http://rocknroll.mcom.com/users/marek/publish/Gecko/Gecko2Tasks.html
Keywords: topembed

Updated

15 years ago
Keywords: topembed

Updated

15 years ago
Blocks: 176349

Comment 13

15 years ago
Bulk adding topembed keyword.  Gecko/embedding needed.
Keywords: topembed

Updated

15 years ago
Keywords: topembed

Comment 14

15 years ago
moving to 1.4 beta, dependent bugs will be worked on in plug-in branch
Target Milestone: mozilla1.2beta → mozilla1.4beta
(Reporter)

Updated

14 years ago
Depends on: 89270
(Reporter)

Updated

12 years ago
Depends on: 163888
QA Contact: shrir → plugins

Comment 15

6 years ago
I think we can consider this resolved fixed given that our NPAPI plugin implementation has been mature for a while now.
Assignee: serhunt → nobody
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.