Closed
Bug 266525
Opened 20 years ago
Closed 20 years ago
Plugin finder does not work when a page with plugin is opened in background tab
Categories
(Toolkit Graveyard :: Plugin Finder Service, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.8final
People
(Reporter: pavel.penaz, Assigned: doronr)
References
Details
(Keywords: testcase, Whiteboard: [have patch] do we want it?)
Attachments
(2 files, 1 obsolete file)
290 bytes,
text/html
|
Details | |
2.32 KB,
patch
|
jst
:
review+
jst
:
superreview+
asa
:
approval-aviary-
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0
When I open a page with a plugin in a background tab, clicking on the "Install
missing plugin" button does not do anything, the plugin information bar just
disappears.
Reproducible: Always
Steps to Reproduce:
1. Have tabs set to open in the background
2. Open http://www.macromedia.com/shockwave/welcome/ in tab
3. Click on the button "Install missing plugin"
Actual Results:
Plugin information bar disappears
Expected Results:
Plugin finder should be invoked
Reporter | ||
Comment 1•20 years ago
|
||
I should probably add that you have to wait till the page fully loads in the
background tab. If you switch to the tab before the page fully loads, the plugin
finder works as expected.
Comment 2•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041028
Firefox/1.0RC1
Confirming
open the testcase in a background tab and try to find the missing plugin
->NEW
Updated•20 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 3•20 years ago
|
||
Thanks Peter for confirming the bug. I guess this is a rather serious issue,
nominating for blocking FF1.0.
Summary: Plugin finder does not work when the page with plugin is opened in background tab → Plugin finder does not work when a page with plugin is opened in background tab
Reporter | ||
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Comment 4•20 years ago
|
||
Hm, WFM using testcase
plugin finder pops up and tells me "No suiteable plugins were found."
Plugin information bar does not disappear.
Didn't use a new profile.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026
Firefox/1.0RC1
Comment 5•20 years ago
|
||
(In reply to comment #4)
> Hm, WFM using testcase
> plugin finder pops up and tells me "No suiteable plugins were found."
> Plugin information bar does not disappear.
> Didn't use a new profile.
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026
> Firefox/1.0RC1
Open in background, not foreground
Comment 6•20 years ago
|
||
(In reply to comment #5)
> Open in background, not foreground
>
I did that
Comment 7•20 years ago
|
||
Ups, clicked on "Click here to download plugin" :o(. sorry!
Confirm this bug when using "Install missing plugin"
Assignee | ||
Comment 8•20 years ago
|
||
not really a blocker, tabs are an advanced user feature.
Assignee | ||
Comment 9•20 years ago
|
||
this is caused by a tabbrowser "feature" - selecting a tab fires
onLocationChange, and the pfs clears its list, as its expecting a new URL to
have loaded.
Status: NEW → ASSIGNED
Assignee | ||
Comment 10•20 years ago
|
||
Assignee | ||
Comment 11•20 years ago
|
||
Attachment #163855 -
Attachment is obsolete: true
Comment 12•20 years ago
|
||
Comment on attachment 164414 [details] [diff] [review]
move clearing to startDocumentLoad and move closing message to pfs code.
- In pluginInstallerWizard.js:
>+ window.opener.getBrowser().hideMessage(window.opener.getBrowser().selectedBrowser, "top");
> window.opener.getBrowser().reloadTab(gPluginInstaller.mTab);
Might want to store window.opener.getBrowser() in a local here to avoid calling
it 3 times in a row...
r+sr=jst
Attachment #164414 -
Flags: superreview+
Attachment #164414 -
Flags: review+
Assignee | ||
Comment 13•20 years ago
|
||
Comment on attachment 164414 [details] [diff] [review]
move clearing to startDocumentLoad and move closing message to pfs code.
dunno if 1.0 wants this.
Attachment #164414 -
Flags: approval-aviary?
Updated•20 years ago
|
Whiteboard: [have patch] do we want it?
Comment 14•20 years ago
|
||
Comment on attachment 164414 [details] [diff] [review]
move clearing to startDocumentLoad and move closing message to pfs code.
too late for 1.0.
Attachment #164414 -
Flags: approval-aviary? → approval-aviary-
Comment 15•20 years ago
|
||
in that case, this can't be a blocker for 1.0.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Reporter | ||
Comment 16•20 years ago
|
||
Could this be checked into Aviary now, is it safe enough? Thanks
Assignee | ||
Comment 17•20 years ago
|
||
Its up to aviary drivers to decide.
Comment 19•20 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041118 Firefox/1.0
Confirmed on Linux, too.
Assignee | ||
Comment 20•20 years ago
|
||
checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Firefox → Toolkit
Updated•10 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•