TypeError when calling phantomcss.compareAll() about phantomcss HOT 7 CLOSED

It should work on Windows. I built it on Windows.. Just had a quick gander, no repro for me with the demo :(

Can't say for sure, you seem to be using a npm installed CasperJS 'C:/Users/Kriss/AppData/Roaming/npm/node_modules/casperjs/modules/casper.js:1553' which is reasonable - but I wonder if the version you're using is different in some way, perhaps there has been a breaking change in CasperJS recently.

Could you try using (Windows only) the casperjs.bat file?

casperjs.bat test demo/testsuite.js

from phantomcss.

I get the same error when I invoke the demo test suite with casperjs.bat. Is there an alternate way to install CasperJS that you think I should try?

from phantomcss.

Not sure it's the CasperJS install then. I can't think of any other possible solutions, maybe some weird localhost port conflict? Try running the demo tests without localhost running. Pulling at straws tbh. Sorry I can't be more helpful.

from phantomcss.

I'm running into this issue. It's extremely strange and exceedingly hard to reproduce. Probably not a PhantomCSS bug, but I really have no idea at this point. I'm posting less to ask for a solution and more to document my descent into madness.

Using:

• casperjs 1.1.0-beta3 (via npm)
• phantomjs 1.9.17 (via dependency of casperjs)
• phantomcss 0.10.1 (via npm)

What's going on is that for some reason, Casper.prototype.fill seems to be getting clobbered by some other value, which can change depending on completely unrelated alterations to other parts of my test suite. Because of this, I'm starting to suspect some sort of memory allocation bug.

I've been looking for exactly where this happens, and I tracked it to this call within casper.captureSelector. Note the console.logs:

Casper.prototype.getElementBounds = function getElementBounds(selector) {
    "use strict";
    this.checkStarted();
    if (!this.exists(selector)) {
        throw new CasperError("No element matching selector found: " + selector);
    }
    var clipRect = this.callUtils("getElementBounds", selector);
console.log('getelementbounds1', Casper.prototype.fill);
    if (!utils.isClipRect(clipRect)) {
        throw new CasperError('Could not fetch boundaries for element matching selector: ' + selector);
    }
console.log('getelementbounds2', Casper.prototype.fill);
    return clipRect;
};

The output is as follows:

getelementbounds1 function GET(formSelector, vals, submit) {
    "use strict";
    return this.fillForm(formSelector, vals, {
        submit: submit,
        selectorType: 'names'
    });
}
getelementbounds2 984

A couple interesting things here. First is that at some point earlier, the function name has been replaced with what appears to be an HTTP verb. Second is that after utils.isClipRect is called, the value on Casper.prototype is replaced entirely with 984, which is the width of the element.

All of this leads to my preliminary hypothesis that for some reason, the section of memory in which Casper.prototype resides has somehow been double-allocated.

That's all I've got for now.

from phantomcss.

Note that I tried the same repo on Windows and OSX, and only ran into this issue on the Windows machine.

from phantomcss.

I have a minimal reproducing test case: https://github.com/smrq/phantomcss-wtf

from phantomcss.

I've run into this issue and after some research found a quickfix: https://groups.google.com/forum/#!topic/casperjs/i39TtMnwgJs
Seems like casperjs issue with casper.fill on windows.

I've created a pull-request with a fix: #127

from phantomcss.