Closed
Bug 952824
Opened 12 years ago
Closed 11 years ago
Nightly Plug-in Finder's Next button is clickable before a plug-in is found
Categories
(Toolkit Graveyard :: Plugin Finder Service, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: daft.goon, Unassigned)
Details
Attachments
(1 file)
|
232.96 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20131221030204
Steps to reproduce:
Install a fresh copy of Firefox Nightly(version 29.0a1), go to YouTube.com, and since Adobe Flash is not installed, Firefox will ask to install the missing plug-in. Click "Install missing plug-in."
Actual results:
While the Plug-in Finder service searches for a valid plug-in, the "next" button is visible and can be clicked on.
Expected results:
The Next button should not light up, or be clickable. It should only become clickable when it has finished searching for a plug-in.
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Component: Untriaged → Plugin Finder Service
Ever confirmed: true
Product: Firefox → Toolkit
Comment 1•11 years ago
|
||
Bug 836415 has now removed the Plugin Finder Service (PFS) from Firefox. As a result, I'm closing all the remaining PFS bugs.
If you're getting this bugmail for an ancient PFS bug, the basic summary of the world today is:
* NPAPI plugins are a dying technology
* PFS was already restricted to assisting with only the 4 most common plugins
* Sites commonly provide their own UI for install a required plugin
* Mozilla is generally focusing on improving the web platform so that proprietary plugins are not required.
(Note that "plugins" are a completely separate from "browser extensions", such at those found on addons.mozilla.org. The latter are not going anywhere, and are not impacted by the removal of PFS.)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•11 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•