TwinShot
Unsafe JavaScript attempt to access frame with URL
from frame withURL
.
Domains, protocols and ports must match.
Huh?
Thank you!
Best Answer Rob , 18 January 2013 - 01:44 AM
Hi Suzy,
I tested each of the four videos in both Chrome and Firefox to see if there's any error message thrown, or any irregularities. Everything was perfect for both and no errors. My guess is that your browser may simply not have loaded the javascript correctly and become stuck in the browser's cache. If you get this error again, please screenshot it and include that here.
Go to the full post
Posted 18 January 2013 - 12:26 AM
TwinShot
Unsafe JavaScript attempt to access frame with URL
from frame withURL
.
Domains, protocols and ports must match.
Huh?
Thank you!
Posted 18 January 2013 - 01:16 AM
Hi Suzy, this sounds like a security warning, did you put in the full url for the video? Looking on your site I can't see the message appearing in firefox, which browser are you using?
Posted 18 January 2013 - 01:20 AM
Hi James. Got the error in Chrome. Just checked, all urls are complete.
Posted 18 January 2013 - 01:44 AM
From the look of this post i found it seems like a security setting in chrome which is activated when using the web dev tool kit. It shouldn't harm the actual page content though, so your visitors will still see the site as usual. I checked in Chrome on a Mac but i couldn't get the error to appear.
Posted 18 January 2013 - 01:44 AM Best Answer
Hi Suzy,
I tested each of the four videos in both Chrome and Firefox to see if there's any error message thrown, or any irregularities. Everything was perfect for both and no errors. My guess is that your browser may simply not have loaded the javascript correctly and become stuck in the browser's cache. If you get this error again, please screenshot it and include that here.
Posted 18 January 2013 - 04:15 AM
THANKS, GUYS! I concerned about all of the junk on my error logs. Most of it is from WP BOXER PRO, fatal php lollapalooza. Trying to figure it out now, before I produce my masterpiece.
Posted 06 March 2013 - 11:22 PM
That is a standard warning in Chrome that has to do with crossdomain iframe access. It has nothing to do with your code and should just be ignored ![]()