In protractor.conf.js, the onPrepare() function includes some code to automatically set the size of the browser window (so that DOM elements that are clicked during tests are visible on screen).
In a recent upgrade, it would seem that a change in ChromeDriver now triggers a CSP unsafe-eval warning when it encounters this code.
As an aside, for a while now it seems that both karma and protractor runs default to a full-size Chrome window, so for now we have simply commented out the offending code that attempted to size the window.
It would be nice to track down why Chrome has started resizing itself; as it may be that we can now permanently remove our code that does window sizing?
In
protractor.conf.js
, theonPrepare()
function includes some code to automatically set the size of the browser window (so that DOM elements that are clicked during tests are visible on screen).In a recent upgrade, it would seem that a change in ChromeDriver now triggers a CSP
unsafe-eval
warning when it encounters this code.https://bugs.chromium.org/p/chromedriver/issues/detail?id=1344
As an aside, for a while now it seems that both
karma
andprotractor
runs default to a full-size Chrome window, so for now we have simply commented out the offending code that attempted to size the window.It would be nice to track down why Chrome has started resizing itself; as it may be that we can now permanently remove our code that does window sizing?