Closed Bug 253744 Opened 21 years ago Closed 14 years ago

Polish Plugin Experience - Installer work

Categories

(Firefox :: Installer, defect, P2)

x86
Windows XP
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: chofmann, Unassigned)

Details

break off for installer related work in http://bugzilla.mozilla.org/show_bug.cgi?id=244125 INSTALLER: 2) get the firefox stub installer code landed (from blake) 3) make the stub installer check which plugins are installed (it's a native windows app - can check reg keys etc) 4) provide an additional page to the wizard for both "Easy" and "Custom" installs that lists plugins that were not found on disk (*) to download and install. 5) collect xpis that silently install plugins (i.e. without UI) for use in the installer
Assignee: bugs → firefox
Flags: blocking-aviary1.0PR+
Why is 244125 restricted access?
Let's revise the requirements here to reflect what we're likely to get on time... The new requirements are: - detect existing plugins on the system that *might* work with us... (I am still waiting to see a matrix identifying these posted somewhere) - copy the plugins/xpt files/set up registry keys etc to make them work. Leave the download portion out of the installer for now since it has l10n impact and additional complexity that I'm not convinced we can get working flawlessly in time. Because of the shifting requirements, - for PR, + for 1.0
Flags: blocking-aviary1.0PR-
Flags: blocking-aviary1.0PR+
Flags: blocking-aviary1.0+
Priority: -- → P2
Not a "blocker"
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
QA Contact: bugzilla → installer
Assignee: bross2 → nobody
As it stands currently, we have the plugin finder service to install plugins, as I understand it the plugins we are interested in installing require the user to first agree to a EULA, and the times I have talked with people about getting permission to redistribute plugins it seemed like it isn't going to happen. Comment #2 was implemented as needed and with the new plugin architecture is no longer required so the code was removed. Resolving -> wontfix since there are at the very least dependencies that would first need to be completed before implementing in the installer. If we do get permission to install plugins via the installer I will be more than happy to add this functionality to the installer.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.