907361 - Since last update, can not click links in Facebook game

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[kwestbroker]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130814063812

Steps to reproduce:

Since the last update, I can not click the links in the following facebook game, Dynasty Baseball, https://apps.facebook.com/dynasty-baseball-cl/en/baseball/simulation/index


Actual results:

You can click on the boxes, but the links do not actually work.  It works fine in IE and Chrome.  I have to open the links in a new window to get them to work.


Expected results:

The links should click through to the next page.

Comment 1

[Paul Silaghi, QA [:pauly]]

(In reply to kwestbroker from comment #0)
> You can click on the boxes, but the links do not actually work
What boxes ?

I click on the 'Play the game' button, a security warning shows up and finally the game won't start. Is this the issue you see ?

Comment 2

[kwestbroker]

No, during the game, you can not click on any of the buttons in the game, like go to my league page, or play an opponent, or join a league.

Comment 3

[Paul Silaghi, QA [:pauly]]

1. Please check if the issue occurs using Firefox in safe mode (with your addons disabled):
http://support.mozilla.com/kb/Safe+Mode

Or on a new, empty profile:
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager

2. If you're still seeing the issue after 1. :
(In reply to kwestbroker from comment #2)
> like go to my league page, or play an opponent, or join a league.
Can't find those buttons. Could you please point me to them?
This is what I see http://img16.imageshack.us/img16/1719/iwxf.png

Comment 4

[kwestbroker]

Next to the highlighted home button, it says Play Ball, Friends, Lineup, etc.  You can not click on them.

Comment 5

[Paul Silaghi, QA [:pauly]]

I finally see your problem, and it's caused apparently by a Firefox feature called "mixed content blocker" - see the doorhanger from the left of the location bar.
But it seems to be fixed on FF 24 (which is currently on beta cycle http://www.mozilla.org/en-US/firefox/beta/) and up.
Tanvi, is this known?

Comment 6

[Tanvi Vyas[:tanvi]]

You can find more information about the Mixed Content Blocker here: https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/.

Firefox 23+ blocks active HTTP subrequests on HTTPS pages.  Chrome and IE have similar mixed content blockers, but the restrictions differ slightly.

From April through July we worked to identify sites that did not function correctly because of Mixed Content Blocker (https://bugzilla.mozilla.org/show_bug.cgi?id=844556).  Facebook games were mentioned a couple times but we did not find any with Mixed Active Content (just Mixed Passive Content which is not blocked by default).  It sounds like this game has Mixed Active Content.

We have fixed a couple things in Firefox 24 that may make the experience better (persist the disable protection decision while you are playing the game - https://bugzilla.mozilla.org/show_bug.cgi?id=902156, navigate top level domain https://bugzilla.mozilla.org/show_bug.cgi?id=902350).  Not sure if those will solve the problem you are having.  QA, can you help test this out on the latest Firefox 24 (or on 25 or 26) to see if "disabling protection" once allows you to play the game?  I do see that the "Play Ball" link has a target=_top, so maybe the two bugs we fixed will solve this issue.

The other thing you could do is contact the game developer and ask them to secure their app so that you won't have this issue.

Comment 7

[Paul Silaghi, QA [:pauly]]

Thanks for clearing things up.

(In reply to Tanvi Vyas [:tanvi] from comment #6)
> QA, can you help test this
> out on the latest Firefox 24 (or on 25 or 26) to see if "disabling
> protection" once allows you to play the game?
Works fine in FF 24 and up even without disabling the protection.

Comment 8

[Ciprian Muresan [:cmuresan], Ecosystem QA]

I cannot reproduce this issue on the latest Firefox release(43.0.4) with the Steps given in the description. Based on this and the last comment I'm marking this as RESOLVED WORKSFORME.