Closed
Bug 258491
Opened 20 years ago
Closed 20 years ago
nsXREDirProvider should expose NS_APP_USER_CHROME_DIR as soon as possible
Categories
(Toolkit :: Startup and Profile System, defect)
Toolkit
Startup and Profile System
Tracking
()
RESOLVED
FIXED
People
(Reporter: darin.moz, Assigned: darin.moz)
References
Details
Attachments
(1 file)
|
(deleted),
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
nsXREDirProvider should expose NS_APP_USER_CHROME_DIR as soon as possible.
right now, nsXREDirProvider does not resolve certain directory keys if the
profile change notification has not yet been broadcasted. this causes problems
for chrome registration since CR can occur after a profile has been selected but
before the profile change notification has been broadcasted. as a result,
XULRunner apps that depend on chrome.rdf in the profile directory can fail to
have their chrome registered.
one way to reproduce this is to start out with no profile, and use firefox -app
to launch a simple XUL app. firefox will attempt to do profile migration, but
that occurs before the profile has been activated. as a result, the XUL apps
chrome is not registered.
|
Assignee | |
Comment 1•20 years ago
|
||
|
|
Assignee | |
Updated•20 years ago
|
Attachment #158233 -
Flags: review?(bsmedberg)
|
||
Updated•20 years ago
|
Attachment #158233 -
Flags: review?(bsmedberg) → review+
|
|
Assignee | |
Comment 2•20 years ago
|
||
fixed-on-trunk
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•