Closed
Bug 191021
Opened 23 years ago
Closed 23 years ago
Put the null plugin back where it belongs
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stdowa+bugzilla, Assigned: timeless)
Details
Attachments
(2 files, 1 obsolete file)
|
653 bytes,
patch
|
asa
:
approval1.3b+
|
Details | Diff | Splinter Review |
|
1.25 KB,
patch
|
timeless
:
review+
asa
:
approval1.3b+
|
Details | Diff | Splinter Review |
With today's Windows installer build, the null plugin isn't being displayed when
a plugin can't be found; about:mozilla doesn't display anything about the null
plugin. The null plugin is located in the GRE plugins dir, but it appears
Mozilla isn't scanning that dir for plugins.
Comment 1•23 years ago
|
||
do we really want the default plugin in the GRE ?
Comment 2•23 years ago
|
||
hmm...different embedders may have overriden their default plugins with their
own implementations so I think we may need to scan the GRE dir in addition to
the app plugins dir but keep the null plugin in the app dir. Also, another
embedding project has asked for a sharable location for plugins so maybe we can
have a system global folder like on Mac or GRE global that embedders can opt in?
Here's the code in nsAppFileLocationProvider that causes the scan of bin/plugins:
197 else if (nsCRT::strcmp(prop, NS_APP_PLUGINS_DIR) == 0)
198 {
199 rv = CloneMozBinDirectory(getter_AddRefs(localFile));
200 if (NS_SUCCEEDED(rv))
201 rv = localFile->AppendRelativeNativePath(PLUGINS_DIR_NAME);
http://lxr.mozilla.org/seamonkey/source/xpcom/io/nsAppFileLocationProvider.cpp#583
Comment 3•23 years ago
|
||
wouldn't it be nice if the plugin code just registered their own directory
service provider :-)
Comment 4•23 years ago
|
||
it could (and I recall it did at one point in time) but embedders requested
finer control
the null plugin we're packaging is really really horrible, we should be
encouraging embedders to replace it by making them opt into using it.
we don't want the null plugin in the gre.
Assignee: peterlubczynski → timeless
Summary: Make Mozilla aware of plugins located in the GRE plugins dir → Put the null plugin back where it belongs
Comment 7•23 years ago
|
||
Comment on attachment 112926 [details] [diff] [review]
put the null plugin back where it belongs
r=peterl
Attachment #112926 -
Flags: review+
Comment on attachment 112926 [details] [diff] [review]
put the null plugin back where it belongs
this is a small build change but it's important for the gre not to include this
file.
Attachment #112926 -
Flags: approval1.3b?
Comment 9•23 years ago
|
||
Comment on attachment 112926 [details] [diff] [review]
put the null plugin back where it belongs
a=asa (on behalf of drivers) for checkin to 1.3beta.
Attachment #112926 -
Flags: approval1.3b? → approval1.3b+
| Assignee | ||
Comment 10•23 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 11•23 years ago
|
||
*sigh* why oh why are the gre packaging files pathwise incompatible with the
mozilla packaging files?
Attachment #112926 -
Attachment is obsolete: true
Comment 12•23 years ago
|
||
timeless, you also need to check this patch in. browser.xpi should no longer
be deleting the npnul32.dll during installation because it's installing it now.
| Assignee | ||
Comment 13•23 years ago
|
||
right, thanks.
drivers: the gre changes currently mean we aren't shipping a null plugin on
windows. given that the null plugin can crash in edge cases that might not be a
bad thing, but most people would probably be annoyed by the you're missing the
null plugin dialog. and it's a usability loss. the patch pair here is simple
and imo worth committing.
Status: RESOLVED → REOPENED
Flags: blocking1.3b?
Resolution: FIXED → ---
| Assignee | ||
Comment 14•23 years ago
|
||
Comment on attachment 113933 [details] [diff] [review]
really put it back where it belongs
this correctly packages the null plugin.
Attachment #113933 -
Flags: review?(ssu)
Attachment #113933 -
Flags: approval1.3b?
| Assignee | ||
Comment 15•23 years ago
|
||
Comment on attachment 113938 [details] [diff] [review]
patch to remove code that deletes npnul32.dll
this prevents the installer from killing the null plugin ... ... ...
Attachment #113938 -
Flags: review+
Attachment #113938 -
Flags: approval1.3b?
Comment 16•23 years ago
|
||
Comment on attachment 113933 [details] [diff] [review]
really put it back where it belongs
a=asa (on behalf of drivers) for checkin to 1.3b.
Attachment #113933 -
Flags: approval1.3b? → approval1.3b+
Comment 17•23 years ago
|
||
Comment on attachment 113938 [details] [diff] [review]
patch to remove code that deletes npnul32.dll
a=asa (on behalf of drivers) for checkin to 1.3beta.
Attachment #113938 -
Flags: approval1.3b? → approval1.3b+
| Assignee | ||
Comment 18•23 years ago
|
||
checked in
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Attachment #113933 -
Flags: review?(ssu)
Comment 20•23 years ago
|
||
Marking Verified Fixed.
Compared the two patches to the checkins:
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=packages-win&root=/cvsroot&subdir=mozilla/xpinstall/packager&command=DIFF_FRAMESET&rev1=1.250&rev2=1.251
and
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=packages-win&root=/cvsroot&subdir=mozilla/xpinstall/packager&command=DIFF_FRAMESET&rev1=1.249&rev2=1.250
Status: RESOLVED → VERIFIED
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•