Open
Bug 408919
Opened 17 years ago
Updated 2 years ago
Broken extensions initialization after landing 392251
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
NEW
People
(Reporter: romaxa, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
3.22 KB,
patch
|
benjamin
:
review-
|
Details | Diff | Splinter Review |
Problem mostly related to embedding api and initialization with XRE_InitEmbedding. Before landing 392251 it was possible to initialize extensions with the next way: Install extension - extension appears in some "extension" dir extmgr->Start - extensions.ini updated nsIComponentRegistrar->AutoRegister - Updated compreg.dat and components form extension folder preloaded... After landing 392251 it is not possible to call LoadBundleDirectories (parse extensions.ini) twice in one session, without restarting. I guess we need to check also extensions.ini modification time and reload it it was changed In attachments proposed fix..
Attachment #293772 -
Flags: review?(benjamin)
Reporter | ||
Comment 1•17 years ago
|
||
Comment on attachment 293772 [details] [diff] [review] Possible fix. Ups, wrong version...
Attachment #293772 -
Attachment is obsolete: true
Attachment #293772 -
Flags: review?(benjamin)
Reporter | ||
Comment 2•17 years ago
|
||
Attachment #293778 -
Flags: review?(benjamin)
Comment 3•17 years ago
|
||
Comment on attachment 293778 [details] [diff] [review] This should be better This is not the correct solution. If you wish, you can make LoadBundleDirecotories forward the request to mAppProvider before responding, but I don't want to institutionalize the extensions.ini file or make embedders write one.
Attachment #293778 -
Flags: review?(benjamin) → review-
Component: XRE Startup → Startup and Profile System
QA Contact: xre.startup → startup
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•