Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox v55.0 (Win) and higher can't load .swf files from an iFrame (Kongregate, Facebook)

  • 7 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: cgascons

more options

Hi,

I've been looking around for a solution to this problem in this forum, StackOverflow, Facebook Support and Kongregate Engineers, none of them know what to do.

This is not a problem trying to run local .swf files, it's a problem trying to load them from a remote server (i.e. cdn).

Since we can not share the Kongregate nor the Facebook url because is a development link and there's no public access to it, this link (https://we.tl/JZBWOhs4Lh) contains the two files of the simplest project I could imagine (2KB) which is a Test.html and Test.swf file, the swf file will just display the following text: "Testing SWF!".

If we access from Firefox (v55.0) on a Windows computer to the local file or to the raw url where the swf is placed (https://d1qzmgnbw7y2pl.cloudfront.net/Test/Test.html) the content can be accessed without issues (it will ask if we want to use Flash which is fine), on the other hand, we have setup a kongregate project and also a Facebook project (the configuration is set to load the html as an iFrame), and pointing to that very same url the game just won't load it from there, it will display a black screen.

I have already changed the http_https_ parameter and we still experience the issue. This is affecting lots of users on our end, I'd highly appreciate any advise.

Thanks beforehand,

Hi, I've been looking around for a solution to this problem in this forum, StackOverflow, Facebook Support and Kongregate Engineers, none of them know what to do. This is not a problem trying to run local .swf files, it's a problem trying to load them from a remote server (i.e. cdn). Since we can not share the Kongregate nor the Facebook url because is a development link and there's no public access to it, this link (https://we.tl/JZBWOhs4Lh) contains the two files of the simplest project I could imagine (2KB) which is a Test.html and Test.swf file, the swf file will just display the following text: "Testing SWF!". If we access from Firefox (v55.0) on a Windows computer to the local file or to the raw url where the swf is placed (https://d1qzmgnbw7y2pl.cloudfront.net/Test/Test.html) the content can be accessed without issues (it will ask if we want to use Flash which is fine), on the other hand, we have setup a kongregate project and also a Facebook project (the configuration is set to load the html as an iFrame), and pointing to that very same url the game just won't load it from there, it will display a black screen. I have already changed the http_https_ parameter and we still experience the issue. This is affecting lots of users on our end, I'd highly appreciate any advise. Thanks beforehand,

선택된 해결법

cloudfront.net in general appears to be on that list. personally i can't give you any rationale for this since this is just a users-helping-users forum, but if you want to inquire about this, drop an email to the address at the bottom of that wiki article...

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (7)

more options

The Shockwave Flash plugin has a setting in its Options/Preferences window to "Block dangerous and intrusive Flash content" that is enabled by default.

Any luck with removing the checkmark and disabling this feature?

more options

Hi cor-el, thanks for the (really quick) response!

Indeed, that makes the content work like you said, but I think we'd agree if we said it's not ideal. On the other hand, why some Flash Games can be played without having to activate that option on the same browser? We have a quite large players database that are not comfortable going into those options and disabling that check...

Thanks!

more options
more options

Thanks philipp, I don't quite understand, and I'm really trying to follow here. Does this mean that I can not request our games to be "removed" from that list? As far as I understood, by reading the blocking policies there's a specific criteria that must be met to be blocked:

  • Critical security vulnerabilities.
  • A history of security vulnerabilities.
  • High crash volume.
  • Malicious in nature.
  • Severe performance impact (e.g. adds more than 75% to start-up time).
  • Severe bugs that unintentionally affect core Firefox features.

How did we anyways ended up there? Any guidance will be much appreciated because to be honest I just realized this exists and I'm a bit lost right now.

more options

선택된 해결법

cloudfront.net in general appears to be on that list. personally i can't give you any rationale for this since this is just a users-helping-users forum, but if you want to inquire about this, drop an email to the address at the bottom of that wiki article...

more options

Thanks philipp,

I've sent an e-mail to that address, I'm hoping they reply soon! Thanks for your help so far!

more options

Thanks for your time Philipp, we sent an e-mail to that address and we are already talking to them to solve this. Thanks for your support!