Chrome error when using opener on pop-up window (cross-origin)
I have a local website containing pop-up windows that should be able to access their parents.
Those pop-up windows are opened as seen here:
open("filename.html", 'name', 'scrollbars=yes,width=700');
And I am trying to set them to access their parent window with window.opener
property.
This works fine on Firefox, but not on Chrome, where I get an error:
Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
I've also noticed that when being uploaded to a server it just works fine on both Chrome and Firefox.
How can I make this work on Chrome when running on local? Is there any alternative to window.opener
that allows the child window to acces their parent?
javascript google-chrome window.opener
add a comment |
I have a local website containing pop-up windows that should be able to access their parents.
Those pop-up windows are opened as seen here:
open("filename.html", 'name', 'scrollbars=yes,width=700');
And I am trying to set them to access their parent window with window.opener
property.
This works fine on Firefox, but not on Chrome, where I get an error:
Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
I've also noticed that when being uploaded to a server it just works fine on both Chrome and Firefox.
How can I make this work on Chrome when running on local? Is there any alternative to window.opener
that allows the child window to acces their parent?
javascript google-chrome window.opener
add a comment |
I have a local website containing pop-up windows that should be able to access their parents.
Those pop-up windows are opened as seen here:
open("filename.html", 'name', 'scrollbars=yes,width=700');
And I am trying to set them to access their parent window with window.opener
property.
This works fine on Firefox, but not on Chrome, where I get an error:
Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
I've also noticed that when being uploaded to a server it just works fine on both Chrome and Firefox.
How can I make this work on Chrome when running on local? Is there any alternative to window.opener
that allows the child window to acces their parent?
javascript google-chrome window.opener
I have a local website containing pop-up windows that should be able to access their parents.
Those pop-up windows are opened as seen here:
open("filename.html", 'name', 'scrollbars=yes,width=700');
And I am trying to set them to access their parent window with window.opener
property.
This works fine on Firefox, but not on Chrome, where I get an error:
Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
I've also noticed that when being uploaded to a server it just works fine on both Chrome and Firefox.
How can I make this work on Chrome when running on local? Is there any alternative to window.opener
that allows the child window to acces their parent?
javascript google-chrome window.opener
javascript google-chrome window.opener
asked Nov 23 '18 at 10:26
Biomehanika
770827
770827
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I'm having the same problem with a project... My temporal-solution was to set up a local server, for example:
Download http-server:
$ npm install http-server -g
Look for the project main folder in the console and type:
$ http-server
The console will show you in which port you can run your website in local
Now you can use window.opener in Chrome. I'd like to have a better solution!
By the way, another idea is replacing child-windows for modals :)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444906%2fchrome-error-when-using-opener-on-pop-up-window-cross-origin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'm having the same problem with a project... My temporal-solution was to set up a local server, for example:
Download http-server:
$ npm install http-server -g
Look for the project main folder in the console and type:
$ http-server
The console will show you in which port you can run your website in local
Now you can use window.opener in Chrome. I'd like to have a better solution!
By the way, another idea is replacing child-windows for modals :)
add a comment |
I'm having the same problem with a project... My temporal-solution was to set up a local server, for example:
Download http-server:
$ npm install http-server -g
Look for the project main folder in the console and type:
$ http-server
The console will show you in which port you can run your website in local
Now you can use window.opener in Chrome. I'd like to have a better solution!
By the way, another idea is replacing child-windows for modals :)
add a comment |
I'm having the same problem with a project... My temporal-solution was to set up a local server, for example:
Download http-server:
$ npm install http-server -g
Look for the project main folder in the console and type:
$ http-server
The console will show you in which port you can run your website in local
Now you can use window.opener in Chrome. I'd like to have a better solution!
By the way, another idea is replacing child-windows for modals :)
I'm having the same problem with a project... My temporal-solution was to set up a local server, for example:
Download http-server:
$ npm install http-server -g
Look for the project main folder in the console and type:
$ http-server
The console will show you in which port you can run your website in local
Now you can use window.opener in Chrome. I'd like to have a better solution!
By the way, another idea is replacing child-windows for modals :)
answered Dec 30 '18 at 19:04
SazLamas
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444906%2fchrome-error-when-using-opener-on-pop-up-window-cross-origin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown