Note that there are some explanatory texts on larger screens.

plurals
  1. POChrome (not in app) - facebook error Unsafe JavaScript attempt
    text
    copied!<p>I came across this weird bug in the facebook.com page where the AJAX loaded parts (or however you call the technique facebook uses) didn't load (e.g. the chat, the notifications etc.).</p> <p>When I fired up the developer's console, it gave me this JavaScript error: </p> <pre><code>Unsafe JavaScript attempt to access frame with URL https://www.facebook.com/ai.php[*] from frame with URL https://www.facebook.com/. Domains, protocols and ports must match. </code></pre> <p>*stripped quite a long base64-esque part - I think that's login data so I won't publish that.</p> <p>I tried googling it and I came across several similar problems, so I dug in some more not to double post, but the other's errors where thrown when they were using the API of facebook via some kind of app. I don't do that, I just use <strong>Chrome 20.0.1132.47</strong> (<em>Mac</em>) to visit the facebook.com page. </p> <p>The error was explained on the other posts as a security measure by Chrome (and apparently Safari, too) to prevent some cookies inside a frame to be saved outside the frame. Preventing XSS and whatnot.</p> <h2>THE POSTS I FOUND:</h2> <p><a href="https://stackoverflow.com/questions/3577947/facebook-gives-unsafe-javascript-attempt-to-access-frame-with-url-error-in-chr">Facebook gives &quot;Unsafe JavaScript attempt to access frame with URL&quot; error in Chrome</a> </p> <p><a href="https://stackoverflow.com/questions/9167371/unsafe-javascript-attempt-to-access-frame-when-using-secure-browsing-on-facebook">Unsafe JavaScript attempt to access a frame when using secure browsing on Facebook</a> </p> <p><a href="https://stackoverflow.com/questions/10629875/the-channel-file-and-cdn">The channel file and CDN</a></p> <h2>tl;dr:</h2> <p>facebook call in Chrome 20 (mac) gives error usually only given on js API calles (security measure against xss)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload