This repository has been archived by the owner. It is now read-only.

Unsafe JavaScript attempt to access frame in 1.9.8 #12697

Closed
artjomb opened this Issue Nov 1, 2014 · 56 comments

Comments

Projects
None yet
@artjomb

artjomb commented Nov 1, 2014

I see some questions on StackOverflow with Unsafe JavaScript attempt to access frame notices with the new PhantomJS version 1.9.8. I have created a small sample script

var page = require('webpage').create();

// notices disappear when removing the event handler
page.onConsoleMessage = function(msg) {
    console.log(msg.length);
};

page.open("http://google.com/", function(status) {
    page.evaluate(function() {
        function embedImg(org) {
            var img = new Image();
            img.src = org.src;
            img.onload = function() {
                var canvas = document.createElement("canvas");
                canvas.width = this.width;
                canvas.height = this.height;

                var ctx = canvas.getContext("2d");
                ctx.drawImage(this, 0, 0);

                var dataURL = canvas.toDataURL("image/png");

                org.src = dataURL;
                // notices disappear when removing the console.log
                console.log(dataURL);
            }
        }
        var imgs = document.getElementsByTagName("img");
        for (var index=0; index < imgs.length; index++) {
            embedImg(imgs[index]);
        }
    });
    // notices disappear when 'asynchronizing' exit using setTimeout even with a 0 timeout
    //setTimeout(function(){
        phantom.exit()
    //}, 0);
});

This didn't happen in 1.9.7.

Complete error

Unsafe JavaScript attempt to access frame with URL  from frame with URL file://test46_google.js. Domains, protocols andports must match.

Unsafe JavaScript attempt to access frame with URL  from frame with URL file://test46_google.js. Domains, protocols andports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

This is the smallest code that reproduces this for CasperJS (run as casperjs test script.js):

casper.test.begin('test unsafe', function(test) {
    test.done();
});

I suspect this happens when PhantomJS tries to exit, but there is currently data exchange between page context and outer context. I've also searched for the error string in the sources here on github, but couldn't find any reference for this notice. The notices don't go way when PhantomJS is run with --web-security=false and similar.

@artjomb artjomb changed the title from Unsafe JavaScript attempt to access frame to Unsafe JavaScript attempt to access frame in 1.9.8 Nov 1, 2014

@docbrown

This comment has been minimized.

Show comment
Hide comment
@docbrown

docbrown Nov 4, 2014

The setTimeout work-around only worked for me if I closed the page first. So I came up with this wrapper function that also halts the script as expected:

function exit(code) {
    if (page) page.close();
    setTimeout(function(){ phantom.exit(code); }, 0);
    phantom.onError = function(){};
    throw new Error('');
}

docbrown commented Nov 4, 2014

The setTimeout work-around only worked for me if I closed the page first. So I came up with this wrapper function that also halts the script as expected:

function exit(code) {
    if (page) page.close();
    setTimeout(function(){ phantom.exit(code); }, 0);
    phantom.onError = function(){};
    throw new Error('');
}
@vitalets

This comment has been minimized.

Show comment
Hide comment
@vitalets

vitalets Nov 6, 2014

+1
waiting for fix

vitalets commented Nov 6, 2014

+1
waiting for fix

@buberdds

This comment has been minimized.

Show comment
Hide comment

buberdds commented Nov 6, 2014

+1

@jsotuyod

This comment has been minimized.

Show comment
Hide comment

jsotuyod commented Nov 6, 2014

+1

@v4l3r10

This comment has been minimized.

Show comment
Hide comment

v4l3r10 commented Nov 6, 2014

+1

@Vitallium Vitallium added this to the FutureRelease milestone Nov 6, 2014

@Vitallium Vitallium self-assigned this Nov 6, 2014

@mickaelandrieu

This comment has been minimized.

Show comment
Hide comment
@mickaelandrieu

mickaelandrieu Nov 6, 2014

Contributor

@Vitallium : would you mind to ping CasperJs team when the issue is resolved ?
We may want to add the (probably) last 1.9.x release of phantomjs support for our 1.1 release.

Sorry to not help, I'm not very easy with C++, thank you for the great job you have done 👍

Contributor

mickaelandrieu commented Nov 6, 2014

@Vitallium : would you mind to ping CasperJs team when the issue is resolved ?
We may want to add the (probably) last 1.9.x release of phantomjs support for our 1.1 release.

Sorry to not help, I'm not very easy with C++, thank you for the great job you have done 👍

@Vitallium

This comment has been minimized.

Show comment
Hide comment
@Vitallium

Vitallium Nov 6, 2014

Collaborator

@mickaelandrieu yeah, sure.

Collaborator

Vitallium commented Nov 6, 2014

@mickaelandrieu yeah, sure.

@Vitallium

This comment has been minimized.

Show comment
Hide comment
Collaborator

Vitallium commented Nov 6, 2014

@juanpabloaj

This comment has been minimized.

Show comment
Hide comment
@juanpabloaj

juanpabloaj Nov 12, 2014

a short example of this problem.

If I copy and paste this code in the phantomjs "interpret"

var webPage = require('webpage');
var page = webPage.create();

page.open("http://www.google.com", function start(status) {
  page.render('google_home.jpeg', {format: 'jpeg', quality: '100'});
  phantom.exit();
});

I get this

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:. Domains, protocols and ports must match.

a short example of this problem.

If I copy and paste this code in the phantomjs "interpret"

var webPage = require('webpage');
var page = webPage.create();

page.open("http://www.google.com", function start(status) {
  page.render('google_home.jpeg', {format: 'jpeg', quality: '100'});
  phantom.exit();
});

I get this

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:. Domains, protocols and ports must match.

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file:. Domains, protocols and ports must match.

Vitallium added a commit that referenced this issue Nov 16, 2014

Don't change the URL of the main execution context on exit.
We shouldn't change the URL of the main execution context.
Because this will change security policy of our main frame which leads to the following message: `Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://bla.js. Domains, protocols and ports must match.`

We can fix it by isolating main frame of PhantomJS execution context. We can destroy it separately.

#12697
@ariya

This comment has been minimized.

Show comment
Hide comment
@ariya

ariya Nov 16, 2014

Owner

Fix in 1.9 branch (though it won't be part of any release).

Owner

ariya commented Nov 16, 2014

Fix in 1.9 branch (though it won't be part of any release).

@ariya ariya closed this Nov 16, 2014

@mickaelandrieu

This comment has been minimized.

Show comment
Hide comment
@mickaelandrieu

mickaelandrieu Nov 16, 2014

Contributor

@ariya thanks.
For the casperJS project, this means at this point:
we support from 1.8.2 to 1.9.7 and master branch.

Am I correct considering this bug resolution ?
Is this fix ported to 2.x future release ?

Regards

Contributor

mickaelandrieu commented Nov 16, 2014

@ariya thanks.
For the casperJS project, this means at this point:
we support from 1.8.2 to 1.9.7 and master branch.

Am I correct considering this bug resolution ?
Is this fix ported to 2.x future release ?

Regards

@ariya

This comment has been minimized.

Show comment
Hide comment
@ariya

ariya Nov 17, 2014

Owner

I don't think this bug applies to PhantomJS 2. But better double check and verify it.

Not sure how critical it is for 1.9.8 to be excluded from CasperJS. Despite it's being annoying, the message is only a warning and AFAICS doesn't cause any functionality regression. Does the workaround with async exit solve it for CasperJS?

Owner

ariya commented Nov 17, 2014

I don't think this bug applies to PhantomJS 2. But better double check and verify it.

Not sure how critical it is for 1.9.8 to be excluded from CasperJS. Despite it's being annoying, the message is only a warning and AFAICS doesn't cause any functionality regression. Does the workaround with async exit solve it for CasperJS?

@jsotuyod

This comment has been minimized.

Show comment
Hide comment
@jsotuyod

jsotuyod Nov 17, 2014

The bug does break my use cases for CasperJS (where I'm managing scripts through stdio from another app, and since the message is submitted to stdout, not even stderr, it breaks havoc), and forced me to rollback to 1.9.7.

As far as I'm concerned for my app, I agree with @mickaelandrieu, CasperJS simply does not work with PhantomJS 1.9.8.

The bug does break my use cases for CasperJS (where I'm managing scripts through stdio from another app, and since the message is submitted to stdout, not even stderr, it breaks havoc), and forced me to rollback to 1.9.7.

As far as I'm concerned for my app, I agree with @mickaelandrieu, CasperJS simply does not work with PhantomJS 1.9.8.

@mickaelandrieu

This comment has been minimized.

Show comment
Hide comment
@mickaelandrieu

mickaelandrieu Nov 17, 2014

Contributor

The CasperJS test suite is broken with 1.9.8 release of phantomjs but I will test the workaround.
I prefer "not exclude" a release of phantomjs, need to think about it ...

Thanks for your comment @jsotuyod

Contributor

mickaelandrieu commented Nov 17, 2014

The CasperJS test suite is broken with 1.9.8 release of phantomjs but I will test the workaround.
I prefer "not exclude" a release of phantomjs, need to think about it ...

Thanks for your comment @jsotuyod

DawidJanczak added a commit to DawidJanczak/guard-jasmine that referenced this issue Nov 17, 2014

mantoni added a commit to mantoni/phantomic that referenced this issue Nov 17, 2014

sebastianrosik added a commit to sebastianrosik/gulp-jasmine2-phantomjs that referenced this issue Nov 18, 2014

Update jasmine2-runner.js
This is a workaround for ariya/phantomjs#12697 which is also used in the guard-jasmine project DawidJanczak/guard-jasmine@04ca925
@AlliterativeAlice

This comment has been minimized.

Show comment
Hide comment
@AlliterativeAlice

AlliterativeAlice Nov 18, 2014

Are there binary packages of the fixed 1.9 branch available? Or do we need to build it ourselves if we want to use it?

Are there binary packages of the fixed 1.9 branch available? Or do we need to build it ourselves if we want to use it?

@gniw

This comment has been minimized.

Show comment
Hide comment
@gniw

gniw Nov 19, 2014

I use CasperJS 1.1.0-beta3, and PhantomJS 1.9.8 are installed with homebrew.
It seems that the problem still exist.

casper.test.begin 'open google', (test)->
  casper
    .start 'https://www.google.com', ->
      test.assertTitle 'Google'
    .run ->
      test.done()

It works, but CasperJS (PhantomJS) says "Unsafe Javascript attempt....".

# open google
PASS Page title is: "Google"
PASS 1 test executed in 0.915s, 1 passed, 0 failed, 0 dubious, 0 skipped.
Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file. Domains, protocols and ports must match.

So, I changed my code just a little like below.

casper.test.begin 'open google', (test)->
  casper
    .start 'https://www.google.com', ->
      test.assertTitle 'Google'
    .run ->
      setTimeout ->
        test.done()
        phantom.exit()
      , 0

After that, I got no error.

# open google
PASS Page title is: "Google"

If I should have posted on CasperJS issue, please let me know.

gniw commented Nov 19, 2014

I use CasperJS 1.1.0-beta3, and PhantomJS 1.9.8 are installed with homebrew.
It seems that the problem still exist.

casper.test.begin 'open google', (test)->
  casper
    .start 'https://www.google.com', ->
      test.assertTitle 'Google'
    .run ->
      test.done()

It works, but CasperJS (PhantomJS) says "Unsafe Javascript attempt....".

# open google
PASS Page title is: "Google"
PASS 1 test executed in 0.915s, 1 passed, 0 failed, 0 dubious, 0 skipped.
Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file. Domains, protocols and ports must match.

So, I changed my code just a little like below.

casper.test.begin 'open google', (test)->
  casper
    .start 'https://www.google.com', ->
      test.assertTitle 'Google'
    .run ->
      setTimeout ->
        test.done()
        phantom.exit()
      , 0

After that, I got no error.

# open google
PASS Page title is: "Google"

If I should have posted on CasperJS issue, please let me know.

@corford

This comment has been minimized.

Show comment
Hide comment
@corford

corford Nov 20, 2014

Same problem here. We rely on STDOUT and STDERR from our Casper scripts and this bug hoses that. We'll be forced to stick to 1.9.7 if this fix doesn't make it into a future 1.9 release (unless a reliable workaround for Casper is found)

corford commented Nov 20, 2014

Same problem here. We rely on STDOUT and STDERR from our Casper scripts and this bug hoses that. We'll be forced to stick to 1.9.7 if this fix doesn't make it into a future 1.9 release (unless a reliable workaround for Casper is found)

alebiavati added a commit to Briteweb/gulp-qunit that referenced this issue Dec 7, 2014

@carylewis

This comment has been minimized.

Show comment
Hide comment
@carylewis

carylewis Dec 14, 2014

I tried to use DocBrown's exit code, but got errors related to the page variable not being set, so I whittled it down to this:

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

and I call exit, with exit(0) after the last test.done(); call in the casperjs script.

I hope this helps someone else.

There is something odd about doing this:

If I try this script:

casper.test.begin("Hello, Test!", 1, function(test) {
test.assert(true);
test.done();
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
});

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

which just calls the two lines in exit but inline test.begin() function, I still get the "Unsafe...." error, whereas calling the exit(0); suppresses the error, maybe someone can explain that?

So to be explicit:

// hello-test.js
casper.test.begin("Hello, Test!", 1, function(test) {
test.assert(true);
test.done();
exit(0);
});

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

suppresses the error.

I tried to use DocBrown's exit code, but got errors related to the page variable not being set, so I whittled it down to this:

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

and I call exit, with exit(0) after the last test.done(); call in the casperjs script.

I hope this helps someone else.

There is something odd about doing this:

If I try this script:

casper.test.begin("Hello, Test!", 1, function(test) {
test.assert(true);
test.done();
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
});

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

which just calls the two lines in exit but inline test.begin() function, I still get the "Unsafe...." error, whereas calling the exit(0); suppresses the error, maybe someone can explain that?

So to be explicit:

// hello-test.js
casper.test.begin("Hello, Test!", 1, function(test) {
test.assert(true);
test.done();
exit(0);
});

function exit(code) {
setTimeout(function(){ phantom.exit(code); }, 0);
phantom.onError = function(){};
}

suppresses the error.

nicksay added a commit to nicksay/spfjs that referenced this issue Sep 27, 2015

Prevent spurious output warnings in the PhantomJS runner for Jasmine 2.3
As described in ariya/phantomjs#12697, PhantomJS runs can output spurious
warnings to the console starting with `Unsafe Javascript attempt`.  Using
a `setTimeout` to call `phantom.exit` immediately after removing the global
`onError` handler eliminates these messages.

Progress on #364
@ppbntl19

This comment has been minimized.

Show comment
Hide comment
@ppbntl19

ppbntl19 Oct 2, 2015

use

"phantomjs": "^1.9.9"

for casperJs

casperjs --ssl-protocol=tlsv1 test  run.js

ppbntl19 commented Oct 2, 2015

use

"phantomjs": "^1.9.9"

for casperJs

casperjs --ssl-protocol=tlsv1 test  run.js
@wannabehero

This comment has been minimized.

Show comment
Hide comment
@wannabehero

wannabehero Oct 13, 2015

workaround from @kolarski actually works.
I've spent just seconds 👍

workaround from @kolarski actually works.
I've spent just seconds 👍

@Heart1010

This comment has been minimized.

Show comment
Hide comment
@Heart1010

Heart1010 Oct 13, 2015

@spronin Can you please tell me where we should place this workaround exactly?

@spronin Can you please tell me where we should place this workaround exactly?

@wannabehero

This comment has been minimized.

Show comment
Hide comment
@wannabehero

wannabehero Oct 13, 2015

childProcess.execFile(casperPath, childArgs, function (err, stdout, stderr) {
  //this is so ugly, but works
  var resp = stdout.replace(new RegExp('Unsafe JavaScript attempt to access frame with URL.*','g'), '').trim();
});

You know, this is very ugly and just suppresses the warning.
So not sure if it is a fix that should be included in production :)

childProcess.execFile(casperPath, childArgs, function (err, stdout, stderr) {
  //this is so ugly, but works
  var resp = stdout.replace(new RegExp('Unsafe JavaScript attempt to access frame with URL.*','g'), '').trim();
});

You know, this is very ugly and just suppresses the warning.
So not sure if it is a fix that should be included in production :)

@zackw zackw added 1.x Bug and removed old.Priority-High labels Oct 14, 2015

@zackw zackw removed this from the FutureRelease milestone Oct 14, 2015

nathanboktae added a commit to nathanboktae/mocha-phantomjs that referenced this issue Oct 20, 2015

JaimeChavarriaga added a commit to JaimeChavarriaga/headless-jasmine-sample that referenced this issue Nov 7, 2015

Update run-jasmine.js
Exit when the page cannot be loaded.
Avoid unnecessary warnings when the PhantomJS is closing. see: ariya/phantomjs#12697
@ekkis

This comment has been minimized.

Show comment
Hide comment
@ekkis

ekkis Nov 18, 2015

as suggested by some, I downgraded to phantomjs-1.9.7-15 but I still get the warnings. I'm running mocha with grunt and the grunt-mocha-phantomjs plugin

ekkis commented Nov 18, 2015

as suggested by some, I downgraded to phantomjs-1.9.7-15 but I still get the warnings. I'm running mocha with grunt and the grunt-mocha-phantomjs plugin

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 18, 2015

I'm running into the same issue as @ekkis . Running the same set-up.

After upgrading to latest versions of mocha-phantomjs@4.0.1 and phantomjs@1.9.18 also produces warnings.

I'm running into the same issue as @ekkis . Running the same set-up.

After upgrading to latest versions of mocha-phantomjs@4.0.1 and phantomjs@1.9.18 also produces warnings.

@ekkis

This comment has been minimized.

Show comment
Hide comment
@ekkis

ekkis Nov 18, 2015

@hyprstack, if you're using the grunt-mocha-phantomjs plugin, I think the issue is that even though you may downgrade the version of phantomjs in your project, the plugin still uses the latest version. I have an open issue here: jdcataldo/grunt-mocha-phantomjs#47 to figure out how to get the plugin to downgrade

ekkis commented Nov 18, 2015

@hyprstack, if you're using the grunt-mocha-phantomjs plugin, I think the issue is that even though you may downgrade the version of phantomjs in your project, the plugin still uses the latest version. I have an open issue here: jdcataldo/grunt-mocha-phantomjs#47 to figure out how to get the plugin to downgrade

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 18, 2015

@ekkis I am. However for the time being I've gone a created a grunt task to regex through the mocha.json file created and remove those lines. It works although I'm more concerned about why those messages are showing up in the first place.

@ekkis I am. However for the time being I've gone a created a grunt task to regex through the mocha.json file created and remove those lines. It works although I'm more concerned about why those messages are showing up in the first place.

@ekkis

This comment has been minimized.

Show comment
Hide comment
@ekkis

ekkis Nov 18, 2015

I don't find a mocha.json in my project. did you modify the package.json of the node_modules/grunt-mocha-phantomjs to change the dependency on phantomjs? to what?

ekkis commented Nov 18, 2015

I don't find a mocha.json in my project. did you modify the package.json of the node_modules/grunt-mocha-phantomjs to change the dependency on phantomjs? to what?

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 18, 2015

@ekkis sorry, forgot to mention that my mocha.json file is generated by the output option in the grunt-mocha-phantomjs plugin as a result of running the task. I then regex through the file and remove those lines so the tests pass in the CI.

@ekkis sorry, forgot to mention that my mocha.json file is generated by the output option in the grunt-mocha-phantomjs plugin as a result of running the task. I then regex through the file and remove those lines so the tests pass in the CI.

@ekkis

This comment has been minimized.

Show comment
Hide comment
@ekkis

ekkis Nov 19, 2015

@hyprstack, jdcataldo looked into the issue and fixed it. you can uninstall/reinstall the grunt-mocha-phantomjs plugin and the warnings will be gone. it worked for me.

ekkis commented Nov 19, 2015

@hyprstack, jdcataldo looked into the issue and fixed it. you can uninstall/reinstall the grunt-mocha-phantomjs plugin and the warnings will be gone. it worked for me.

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 20, 2015

@ekkis thanks for the head's up. I gave it a try but I'm still getting the error messages. Are you still using phantomjs-1.9.7-15?
I tried it with the versions of mocha-phantomjs-4.0.1 and phantomjs1.9.8 and grunt-mocha-phantomjs-2.0.0

@ekkis thanks for the head's up. I gave it a try but I'm still getting the error messages. Are you still using phantomjs-1.9.7-15?
I tried it with the versions of mocha-phantomjs-4.0.1 and phantomjs1.9.8 and grunt-mocha-phantomjs-2.0.0

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 20, 2015

I should probably upgrade the module to grunt-mocha-phantomjs2.0.1!!

I should probably upgrade the module to grunt-mocha-phantomjs2.0.1!!

@hyprstack

This comment has been minimized.

Show comment
Hide comment
@hyprstack

hyprstack Nov 20, 2015

Yep! Silly me. Forgot to update the version in my package.json. It's working now without logging those nasty messages. Cheers! 👍

Yep! Silly me. Forgot to update the version in my package.json. It's working now without logging those nasty messages. Cheers! 👍

@ekkis

This comment has been minimized.

Show comment
Hide comment
@ekkis

ekkis Nov 20, 2015

oh. yes, the npm uninstall command doesn't edit the package.json to remove the entries, so you have to do it manually

ekkis commented Nov 20, 2015

oh. yes, the npm uninstall command doesn't edit the package.json to remove the entries, so you have to do it manually

@katrotz

This comment has been minimized.

Show comment
Hide comment
@katrotz

katrotz Nov 26, 2015

For casperJS folks, the WA mentioned in this thread worked for me:

casper.run(function() {
    var _this = this;

    _this.page.close();

    setTimeout(function exit(){
        _this.exit(exitStatus);
    }, 0);
});

katrotz commented Nov 26, 2015

For casperJS folks, the WA mentioned in this thread worked for me:

casper.run(function() {
    var _this = this;

    _this.page.close();

    setTimeout(function exit(){
        _this.exit(exitStatus);
    }, 0);
});
@khebbie

This comment has been minimized.

Show comment
Hide comment
@khebbie

khebbie Apr 23, 2016

Hello!

You have a new message, please read http://magliner.eu/my.php?0b5m

klaus@hebsgaard.dk

khebbie commented Apr 23, 2016

Hello!

You have a new message, please read http://magliner.eu/my.php?0b5m

klaus@hebsgaard.dk

@jiji262

This comment has been minimized.

Show comment
Hide comment
@jiji262

jiji262 Jun 3, 2016

I use casperjs 1.1.0beta4, and by default it will use phantomjs 1.9.8.
Also I have the similar error:

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Solution:
replace the phantomjs with 2.1.1 version.
On mac, the position is /usr/local/Cellar/casperjs/1.1-beta4/libexec/phantomjs/bin.

jiji262 commented Jun 3, 2016

I use casperjs 1.1.0beta4, and by default it will use phantomjs 1.9.8.
Also I have the similar error:

Unsafe JavaScript attempt to access frame with URL about:blank from frame with URL file://test46_google.js. Domains, protocols and ports must match.

Solution:
replace the phantomjs with 2.1.1 version.
On mac, the position is /usr/local/Cellar/casperjs/1.1-beta4/libexec/phantomjs/bin.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.