1. Open a page with content-security-policy prohibiting evals.
2. Set a breakpoint and make execution pause on it.
3. Try to evaluate something in the inspector console.
Exception, eval is prohibited.
Related bug: https://bugs.webkit.org/show_bug.cgi?id=60800
Created attachment 124292 [details]
Original bug report for Chromium: http://code.google.com/p/chromium/issues/detail?id=98623
Comment on attachment 124292 [details]
Attachment 124292 [details] did not pass chromium-ews (chromium-xvfb):
Created attachment 124303 [details]
Same patch with a test for the new functionality. It depends on a change in V8 API which is not rolled yet.
Comment on attachment 124303 [details]
Attachment 124303 [details] did not pass chromium-ews (chromium-xvfb):
Committed r106657: <http://trac.webkit.org/changeset/106657>