Closed Bug 785070 Opened 12 years ago Closed 11 years ago

[Mac] plugins.click_to_play doesn't detect whether Silverlight is installed

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Version:
15 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: marcia, Unassigned)

References

Details

This was reported by Netflix, and is specific to Mac. Bug 743102 seems to have been resolved on the Windows side.

STR:
1. Set pref in about:config
2. Visit Netflix or any site that uses Silverlight
3. Receive installation error.
4. Flip the pref back and restart
5. Get the same error, no matter whether I use that profile or a new profile

The resolution on my machine was to completely reinstall Silverlight.  I tried clearing the cache, restarting my machine and various other things, but I couldn't get Silverlight working again on my machine.

Testing with the latest Firefox beta on Mac 10.6.8 using Silverlight Version: 5.1.10411.0, but the Netflix reports were all 14.0.1 users and I was able to repro the problem there as well.
> The resolution on my machine was to completely reinstall Silverlight.

So doing this "fixed" the problem?

Did you test with the latest mozilla-central nightly?
Yes, reinstalling Silverlight on my machine fixed the problem. When I get in the office I will test the behavior on trunk and on other machines.

(In reply to Steven Michaud from comment #1)
> > The resolution on my machine was to completely reinstall Silverlight.
> 
> So doing this "fixed" the problem?
> 
> Did you test with the latest mozilla-central nightly?
Blocks: click-to-play
Should we relnote this issue? Setting QA Contact to Paul Silaghi since he is the QA Lead for Click to Play.
QA Contact: paul.silaghi
Testing with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Firefox/17.0 with Version: 5.1.10411.0, this doesn't appear to be an issue.
I haven't yet had a chance to investigate this bug.

But my gut tells me it may have something to do with a pluginreg.dat file not getting updated when it should be.
Using the pref to make plugins click-to-play shouldn't have any dependencies on pluginreg.dat (see mPluginsClickToPlay in nsPluginHost.cpp).
(In reply to Marcia Knous [:marcia] from comment #4)
> Testing with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0)
> Gecko/17.0 Firefox/17.0 with Version: 5.1.10411.0, this doesn't appear to be
> an issue.

Can you check Aurora as well? Thanks Marcia.
I don't see this bug.

Here's what I see instead (testing with FF 14.0.1 and Silverlight 5.1.10411.0 on OS X 10.6.8 and 10.7.4):

1) Set plugins.click_to_play to 'true' in about:config.
2) Restart browser.
3) Visit a page containing a Silverlight plugin (e.g. http://www.thomaswinzer.com/archivecat/).
4) An error page appears containing this message (among other things):  "Install Microsoft Silverlight to use this application".
5) Set plugins.click_to_play to 'false' in about:config.
6) Restart the browser.
7) Revisit the page from step 3.
8) The Silverlight plugin loads normally.

So the bug I see is that you don't see "Click here to activate plugin" in step 3.
> So the bug I see is that you don't see "Click here to activate plugin" in step 3.

This is fixed in today's mozilla-central nightly:  With it I do see "Click here to activate plugin" in step 3.
Regarding Comment 8, it appears Steven and I got very different results when flipping the pref back. In my case I couldn't get Silverlight to work again unless I reinstalled it running beta.

Since this bug works in nightly, there is nothing really to do other than to recommend to Mac users on 14.0.1 and beta to flip the pref back or reinstall Silverlight if that doesn't work.
(Following up comment #8)

None of these steps makes any change to pluginreg.dat -- which is correct.
As discussed in the Channel meeting, I was asked to test on a few other machines to see if I could reproduce having to reinstall Silverlight after invoking the pref, which is the behavior that I saw on my home machine running 10.6.8.

Using a relatively new Mac mini running 10.8, I was able to repeat my testing steps - this machine did not have a version of Silverlight so I installed Version: 5.1.10411.0 first.

1) Launch 14.0.1 and Set plugins.click_to_play to 'true' in about:config.
2) Restart browser.
3) Go to Netflix and begin trying to play a video.
4) An error page is generated about Thanks for installing and asks me to restart the browser.
5) Set plugins.click_to_play to 'false' in about:config.
6) Restart the browser.
7) Revisit the page from step 3.
8) The Silverlight plugin loads normally and the movie plays.
(In reply to Steven Michaud from comment #8)
> I don't see this bug.
> 
> Here's what I see instead (testing with FF 14.0.1 and Silverlight
> 5.1.10411.0 on OS X 10.6.8 and 10.7.4):
> 
> 1) Set plugins.click_to_play to 'true' in about:config.
> 2) Restart browser.
> 3) Visit a page containing a Silverlight plugin (e.g.
> http://www.thomaswinzer.com/archivecat/).
> 4) An error page appears containing this message (among other things): 
> "Install Microsoft Silverlight to use this application".
> 5) Set plugins.click_to_play to 'false' in about:config.
> 6) Restart the browser.
> 7) Revisit the page from step 3.
> 8) The Silverlight plugin loads normally.
> 
> So the bug I see is that you don't see "Click here to activate plugin" in
> step 3.

I confirm this behavior on FF 14.0.1 and Silverlight 5.1.10411.0 on OS X 10.6.8 and 10.7.4. I'm not able to see Marcia's actual results from comment 0.
Also tested this on:
http://www.vectorlight.net/games/sandmania.aspx
http://www.silverlight.net/showcase/2011/11/imagesurfnet

But everything looks fixed in FF 15b6. Click-to-play notification is properly displayed after the step 3. IMO, this is nothing but a dupe of bug 743102.
Closing this for now as it is not actionable.
Please re-open if this reappears or further information is available.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.