October 27, 2015 at 11:55 am Uncaught SecurityError: Blocked a frame with origin #77386
I used jqxsplitter in an iframe on diffrent domain than the page domain.
but i got this problem:
Uncaught SecurityError: Blocked a frame with origin “http://domaine1.com” from accessing a frame with origin “http://domaine2.com”. Protocols, domains, and ports must match. : jqxsplitter.js:7
Any idea how to resolve this problem.October 28, 2015 at 6:49 am Uncaught SecurityError: Blocked a frame with origin #77429
This is not an issue related to jQWidgets. For more information about it, please refer to the following Stack Overflow topic: http://stackoverflow.com/questions/25098021/securityerror-blocked-a-frame-with-origin-from-accessing-a-cross-origin-frame.
http://www.jqwidgets.com/October 28, 2015 at 11:38 am Uncaught SecurityError: Blocked a frame with origin #77444
Thanks for the fast response!February 8, 2018 at 5:50 pm Uncaught SecurityError: Blocked a frame with origin #98632
Throws the error in $.jqx.applyWidget jqxcore.js
What does createInstance do that is trying to make a request across domains?February 8, 2018 at 6:25 pm Uncaught SecurityError: Blocked a frame with origin #98633
Actually I meant across protocols not domains.
“Blocked a frame with origin “http://” from accessing a frame with origin “file://”. The frame requesting access has a protocol of “http”, the frame being accessed has a protocol of “file”. Protocols must match. applyWidget jqxcore.jsFebruary 9, 2018 at 5:44 am Uncaught SecurityError: Blocked a frame with origin #98639
The error is the same as explained in the aforementioned Stack Overflow topic. We are not sure why it is triggered by calling a jQWidgets-related code, but if you wish, you can share the relevant parts of your source code so that we can review them and provide feedback. However, we recommend addressing the actual reason for the error to be thrown – having iframes with different protocols.
http://www.jqwidgets.com/December 13, 2021 at 5:46 am Uncaught SecurityError: Blocked a frame with origin #121212
Same-Origin Policy (SOP) restricts how a document or script loaded from one origin can interact with a resource from another origin. For example, when Site X tries to fetch content from Site Y in a frame, by default, Site Y’s pages are not accessible due to security reasons, it would be a huge security flaw if you could do it.
How to solve?
The window.postMessage() method provides a controlled mechanism to securely circumvent this restriction. The window.postMessage() safely enables cross-origin communication between Window objects; e.g: between a page and an iframe embedded within it.
const frame = document.getElementById(‘your-frame-id’);
frame.contentWindow.postMessage(/*any variable or object here*/, ‘http://your-second-site.com’);
You must be logged in to reply to this topic.