Content Security Policy and WebDriver

As mentioned at TPAC last week, and in the interest of moving discussions
to the mailing list, I've filed a bug against the spec for how a driver
implementation should act in the presence of a Content Security Policy (
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27223). If I'm reading
things properly, a browser that implements the Content Security Policy spec
browsing a site that has a Content Security Policy can entirely disable the
execution of anonymous JavaScript. This would entirely break the
executeScript and executeAsyncScript commands[1].

Should the WebDriver spec address this particular potential interaction
issue? It seems unfriendly to users to say that sites implementing a
Content Security Policy can't be driven by WebDriver implementations.

--Jim

[1] There's also the side effect that it'll entirely disable existing
driver implementations that rely on JavaScript for their implementations.
At present, this affects at least three shipping implementations:
ChromeDriver, the open-source Firefox driver (likely Marionette too), and
the open-source Internet Explorer driver.