Closed Bug 56231 Opened 24 years ago Closed 22 years ago

"Plugin Downloader Plugin" vs "Default Plug-in"

Categories

(Core Graveyard :: Plug-ins, defect, P3)

Product:
Core Graveyard
Component:
Plug-ins
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID
Milestone:
Future

People

(Reporter: jruderman, Assigned: serhunt)

References

Details

The dialog mentioned in bug 56229 refers to a "plugin downloader plugin", but 
about:plugins says "default plug-in" without explaining what the special plugin 
does.  There is no obvious connection between the two names.

Simple fix: Use both names in one place, or just use one name in both places.

Good fix (IMO): Use the name "default plug-in" in both places, but also explain 
in both places that its purpose is to let the user download other plugins as 
needed.
Target Milestone: --- → Future
Future. Not N6 RTM blocker. Netscape engineer this is assigned to is overburdened.
Another bug that would disappar by removing the Default....err...Plugin
Downloader Plugin ;)
Summary: "Plugin Downloader Plugin" vs "Default Plug-in" → Plugin Downloader Plugin" vs "Default Plug-in
Depends on: 83754
OS: Windows 98 → All
Hardware: PC → All
Summary: Plugin Downloader Plugin" vs "Default Plug-in → "Plugin Downloader Plugin" vs "Default Plug-in"
marking invalid, see bug 56229
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.