Can't test Angular2 apps on FireFox

[7-mb]

After updating Angular JS 1.4.x to Angular 2, Selenium tests can't run anymore via grunt-protractor-runner on Firefox. As soon as AngularJS is loaded, the following error occurs (see Stackoverflow for details):

D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:108
  var template = new Error(this.message);
                 ^
UnknownError: Permission denied to access property "toString"
Build info: version: '2.48.2', revision: '41bccdd', time: '2015-10-09 19:59:12'
System info: host: 'NAGWS72', ip: '192.168.210.23', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_79'
Driver info: driver.version: unknown
    at new bot.Error (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:108:18)
    at Object.bot.response.checkResponse (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:109:9)
    at D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:379:20
    at [object Object].promise.Promise.goog.defineClass.invokeCallback_ (D:/.../node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:1337:14)
    at [object Object].promise.ControlFlow.goog.defineClass.goog.defineClass.abort_.error.executeNext_.execute_ (D:/.../node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:2776:14)
    at [object Object].promise.ControlFlow.goog.defineClass.goog.defineClass.abort_.error.executeNext_ (D:/.../node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:2758:21)
    at goog.async.run.processWorkQueue (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\async\run.js:124:15)
    at process._tickCallback (node.js:366:9)
From: Task: <anonymous>
    at [object Object].pollCondition [as _onTimeout] (D:/.../node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:2233:16)
    at Timer.listOnTimeout (timers.js:92:15)
From: Task: <anonymous wait>
    at [object Object].promise.ControlFlow.goog.defineClass.getSchedule.indent.wait (D:/.../node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:2226:17)
    at [object Object].webdriver.WebDriver.wait (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:716:21)
    at [object Object].to.(anonymous function) [as wait] (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\lib\protractor.js:65:25)
    at global.doLogin (D:\...\nisXplorerConfig.js:44:21)
    at exports.config.onPrepare (D:\...\nisXplorerConfig.js:79:9)
    at D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\lib\util.js:54:41
    at Function.promise (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\q\q.js:650:9)
    at Object.exports.runFilenameOrFn_ (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\lib\util.js:44:12)
    at [object Object].Runner.runTestPreparer (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\lib\runner.js:76:17)
    at Object.exports.run (D:\...\node_modules\grunt-protractor-runner\node_modules\protractor\lib\frameworks\jasmine.js:89:17)

So to isolate the problem I installed the sample Angular 2 Go with Protractor ! and got exactly the same error when I changed browserName: 'chrome' to firefox.

Thus I think this is an issue either by protractor or by selenium?

[alecxe]

FYI, it is not related to a specific firefox version - I've tried with 38,39,40..43. Same problem.

[dnozay]

@jleyba may have some idea.

SeleniumHQ/selenium@0fa587d ?

[alecxe]

@dnozay I've tried with the latest selenium (from the master branch) - same issue. Note that it also fails with directConnect - meaning that it is most likely the firefox-specific issue..thanks!

[dnozay]

created SeleniumHQ/selenium#1416 in case it is a selenium-webdriver issue.

[NickTomlin]

@dnozay awesome, thanks for tracking this down!

[RomanHotsiy]

The same issue here.
I noticed this error appears only on the first query to the page. Fixed this by the following workaround:

beforeEach((done) => {
  browser.get(specUrl);
  $('body').isPresent().then(()=> {
    done();
  }, () => {
    //error skipped
    done();
  })
});

So before each test I do isPresent for body and skip error silently. After that all next queries work fine.

[Virginia770]

it works well in my code, thanks! :)

[juliemr]

Per the discussion on selenium, this looks like something to do with how Angular2 is patching EventTargets.

[juliemr]

Digging in further, I believe the problem is due to zone.js patching EventTarget#addEventListener here: https://github.com/angular/zone.js/blob/39b4a9129af9a07b07d7e86a09a040258019470a/lib/utils.ts#L84

That sets

obj.addEventListener = function (eventName, handler, useCapturing) {
    //Ignore special listeners of IE11 & Edge dev tools, see https://github.com/angular/zone.js/issues/150
    if (handler && handler.toString() !== "[object FunctionWrapper]") ....

The firefox-driver extension also uses addEventListener a lot, such as here: https://github.com/SeleniumHQ/selenium/blob/ab1e647d0fc8fc39e6b00ae94321ab228b6728f2/javascript/firefox-driver/js/evaluate.js#L64

I think the code from the normal site can't access properties from the code from the plugin because they're in different domains, but I need to learn more about Firefox's plugin permissions to debug further.

[juliemr]

Minimal failing example at https://github.com/juliemr/zone-firefox-driver

[juliemr]

I've filed an issue with zone.js: angular/zone.js#234

It may alternatively be possible to change FirefoxDriver to export the listener function from the driver's add-on content script to the page script, to avoid the permissions error, but it seems like the ball is in Zone's court since it's the one patching addEventListener.