Closed Bug 178382 Opened 22 years ago Closed 14 years ago

Freeze nsIXPIDialogService & nsIXPIProgressDialog

Categories

(Core Graveyard :: Embedding: APIs, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jjmata+moz, Assigned: dveditz)

References

Details

Per the 10/31/2002 API review meeting these interfaces are ready to be frozen. Please follow the guidelines outlined in the "How to mark an interface as FROZEN" at http://www.mozilla.org/projects/embedding/HowToFreeze.html
Blocks: 157137
Let's make sure we address Doug's needs for XPI signing first: >> Doug Turner wrote: While adding signing support to XPInstall, I found that i needed to pass the cert name that signed the xpi file to the UI. This is so that the user can see who we think signed the xpi file. This name fits nicely in the packageList paramter of the methods on nsXPIDialogService. Before we freeze this interface, I would like to change the nsXPIDialogService interface such that the organization name of the signer is one of the string in the "packageList" parameter. If we don't do this, I am going to have to create a new interface that embedders are going to have to implement inorder to support signed xpi's. <<
I don't have a lot of problem with Doug's proposal, waiting to hear back from AOL folks. Ultimately people will want more cert information, and at that time we *will* have to invent a couple new interfaces. My only concern is that unlike a signature change the proposed semantic change won't break anything at compile time and might not be detected for a while. As long as the AOL guys are OK with the change that's not really a worry.
QA Contact: depstein → ashishbhatt
QA Contact: ashshbhatt → apis
We don't freeze interfaces anymore.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.