Closed
Bug 389486
Opened 18 years ago
Closed 18 years ago
Move pluginreg.dat to profile directory
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9alpha8
People
(Reporter: mwu, Assigned: mwu)
References
Details
Attachments
(1 file)
|
1.33 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
pluginreg.dat should be per profile in order to have enabled/disabled plugins be per profile. Corrupted pluginreg.dat files are also a source of problems, so this makes using a new profile fix more problems than before.
|
Assignee | |
Comment 1•18 years ago
|
||
Do all embedders provide a profile directory? Should we worry about falling back to another directory for those cases?
Assignee: nobody → michael.wu
Status: NEW → ASSIGNED
Attachment #273688 -
Flags: superreview?(jst)
Attachment #273688 -
Flags: review?(jst)
|
||
Updated•18 years ago
|
Attachment #273688 -
Flags: superreview?(jst)
Attachment #273688 -
Flags: superreview+
Attachment #273688 -
Flags: review?(jst)
Attachment #273688 -
Flags: review+
|
|
Assignee | |
Comment 2•18 years ago
|
||
Checking in modules/plugin/base/src/nsPluginHostImpl.cpp;
/cvsroot/mozilla/modules/plugin/base/src/nsPluginHostImpl.cpp,v <-- nsPluginHostImpl.cpp
new revision: 1.585; previous revision: 1.584
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9beta1
|
||
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•