Unable to pass any challenge in Firefox 50 due to CSP-problems

Challenge Name

Any challenge, both beta and production

Issue Description

The exact same code works in Chrome but not in Firefox. In Firefox, the output just above the tests says that the tests were completed, but tests that had to be run in the iframed phone-view never passes.

According to this message from the console, there’s some problem with CSP which prevents some tests from running properly. Content Security Policy: Directive ‘frame-src’ has been deprecated. Please use directive ‘child-src’ instead.

According to This Stack Overflow-thread, the spec for CSP in iframes is confusing at the moment.

I guess we either should use the, according to the SO-thread above, now deprecated child-src temporarily until Firefox implements the new spec with frame-src again.

Alternatively, we drop firefox support temporarily and hope they fix this soon.

@freeCodeCamp/moderators Any ideas on how to solve this?

Browser Information

• Browser Name, Version: Firefox 50.1.0
• Operating System: Ubuntu 16.04
• Mobile, Desktop, or Tablet: Desktop

Your Code

 <style>
  h2 {
    color: blue;
  }
</style>

<h2>CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

Screenshot

Notice the error message in the console at the bottom of the screen.

The exact same code works just fine in the latest version of Chrome for Ubuntu 16.04.

[dhcodes]

As an update to this, I wouldn’t recommend updating CSP yet because it looks like the frame-src deprecation error currently happening will be fixed when frame-src becomes undeprecated (link to source) very soon.

Fwiw, I also updated the CSP to childSrc to see if it fixes the .css issues with Firefox and while it did remove the CSP error in the console, it does not fix the .css issues. The hunt continues.

[systimotic]

@dhcodes That was suggested in #10749. To me, ideally we fix the jQuery CSS tests in Firefox rather than replace them. I’ll close this, we can discuss the solution further in #10749 👍 Thanks a bunch for the triaging work on this @dhcodes!