Closed
Bug 109002
Opened 23 years ago
Closed 8 years ago
track window creation API change in gtkembed
Categories
(Core Graveyard :: Embedding: APIs, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: danm.moz, Assigned: blizzard)
Details
I just checked in an API change on the trunk that will affects all embedding apps. Until today there were two APIs in use to create new windows: nsIWebBrowserChrome::CreateBrowserWindow and nsIWindowCreator::CreateChromeWindow. They are nearly identical, and I've removed the former one. Most embedding apps implemented the former but not the latter, because until now the latter was required only very rarely, and you may not even have noticed it not working. I think actually that you don't need to do anything. I believe I've moved the window creation callback code from nsIWebBrowserChrome to nsIWindowCreator in every embedded app checked in. But you might want to double-check my work. Just wouldn't want you to not know why things suddenly stopped working.
Updated•23 years ago
|
QA Contact: mdunn → depstein
Updated•22 years ago
|
QA Contact: depstein → carosendahl
Updated•15 years ago
|
QA Contact: carosendahl → apis
Comment 1•8 years ago
|
||
Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•