Move pluginreg.dat to profile directory

RESOLVED FIXED in mozilla1.9alpha8

Status

()

Core
Plug-ins
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: mwu, Assigned: mwu)

Tracking

Trunk
mozilla1.9alpha8
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
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

11 years ago
Created attachment 273688 [details] [diff] [review]
Use profile directory

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

11 years ago
Attachment #273688 - Flags: superreview?(jst)
Attachment #273688 - Flags: superreview+
Attachment #273688 - Flags: review?(jst)
Attachment #273688 - Flags: review+
(Assignee)

Comment 2

11 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
Last Resolved: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9beta1

Updated

11 years ago
Depends on: 390183
You need to log in before you can comment on or make changes to this bug.