Support Forum
Can you find the exact line that throws exception? You can use IE10 debugger for that.
Read the API documentation
It seems to be when I try to "click" on anything after the page has refreshed.
{ waitForElementTop: '>> login' },
{ click: '#languageCycle => .x-btn-split-right', offset: ['100%-5', '50%'] },
{ waitForComponentVisible: '#langTypeMenu' },
{ waitFor: 'PageLoad', trigger: {click: '>> #langTypeMenu #' + locale} }, // Causes page reload
{ waitForElementTop: '>> login' },
// Clicking on anything now results in the error, but typing seems to be working.
//{ click: '#languageCycle => .x-btn-split-right', offset: ['100%-5', '50%'] }, // breaks
Does the page remain on the same domain after refresh (including protocol)?
Read the API documentation
Yes, it stays the same. We're reloading the same application with a different language by adding request_locale to the url.
https://localhost:8080/goToLogin.action?&device=desktop#Application/onReady
https://localhost:8080/goToLogin.action?&device=desktop&request_locale=es#Application/onReady
https://localhost:8080/goToLogin.action?&device=desktop&request_locale=en#Application/onReady
Fixed in the sources, thanks for the report! It was a 3.0.0 regression indeed. Please verify in the next nightly build.
Read the API documentation