I've incorporated Vimeo into a WordPress theme I'm building, and I get these errors:
Unsafe JavaScript attempt to access frame with URL / from frame with URL . Domains, protocols and ports must match.
Unsafe JavaScript attempt to access frame with URL / from frame with URL ;byline=0&portrait=0. Domains, protocols and ports must match.
It also (I think) is the reason for the page still loading: /
I've incorporated Vimeo into a WordPress theme I'm building, and I get these errors:
Unsafe JavaScript attempt to access frame with URL http://themes.ibrogram.com/beta/blog/ from frame with URL http://player.vimeo.com/video/4749536. Domains, protocols and ports must match.
Unsafe JavaScript attempt to access frame with URL http://themes.ibrogram.com/beta/blog/ from frame with URL http://player.vimeo.com/video/28496744?title=0&byline=0&portrait=0. Domains, protocols and ports must match.
It also (I think) is the reason for the page still loading: http://themes.ibrogram.com/beta/blog/
Share Improve this question edited Apr 25, 2013 at 14:40 bfavaretto 71.9k18 gold badges117 silver badges159 bronze badges asked Sep 15, 2011 at 22:11 daryldaryl 15.2k21 gold badges68 silver badges93 bronze badges 2- stackoverflow.com/questions/4324108/… – Dave Newton Commented Sep 15, 2011 at 22:15
- It's working fine for me, page loads fine, video plays fine. No console errors. – Rusty Jeans Commented Sep 15, 2011 at 22:15
1 Answer
Reset to default 14Read something about Javascript access security here:
- http://javascript.about.com/od/reference/a/frame3.htm
- Unsafe JavaScript attempt to access frame warning in Safari
- "Unsafe JavaScript attempt to access frame with URL..." error being continuously generated in Chrome webkit inspector
- http://blog.chromium.org/2008/12/security-in-depth-local-web-pages.html
Specifically about implementing Vimeo and JavaScript unsafe access, I found this on a discussion on the Vimeo forums:
If you're using a webkit browser (Safari or Chrome) that error is actually coming from the Webkit Inspector trying to access the iframe (the Webkit Inspector is actually written in HTML and Javascript).
The thing to make sure is that you can't call any of the api or addEvent methods on the iframe until the player has finished loading. As per the example, you need to add the "onLoad" event first and then execute your code inside of that handler.
And second, I checked link you provided, and it loads fast and fine to me, so it is definitely not reason why you keep having this page loading long time