LayoutTests/http/tests/security/isolatedWorld/bypass-main-world-csp-for-inline-script-expected.txt - Issue 137233005: CSP: Improve blocked inline script error message.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: LayoutTests/http/tests/security/isolatedWorld/bypass-main-world-csp-for-inline-script-expected.txt

Issue 137233005: CSP: Improve blocked inline script error message. (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Yay. Created 6 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « LayoutTests/http/tests/security/contentSecurityPolicy/srcdoc-doesnt-bypass-script-src-expected.txt ('k') | LayoutTests/inspector/debugger/debugger-pause-on-blocked-event-handler-expected.txt » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 CONSOLE MESSAGE: line 22: Injecting in main world: this should fail.	1 CONSOLE MESSAGE: line 22: Injecting in main world: this should fail.

2 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'".	2 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'". Either t he 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is r equired to enable inline execution.

3	3

4 CONSOLE MESSAGE: line 26: Injecting into isolated world without bypass: this sho uld fail.	4 CONSOLE MESSAGE: line 26: Injecting into isolated world without bypass: this sho uld fail.

5 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'".	5 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'". Either t he 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is r equired to enable inline execution.

6	6

7 CONSOLE MESSAGE: line 30: Starting to bypass main world's CSP: this should pass!	7 CONSOLE MESSAGE: line 30: Starting to bypass main world's CSP: this should pass!

8 CONSOLE MESSAGE: line 1: EXECUTED in isolated world.	8 CONSOLE MESSAGE: line 1: EXECUTED in isolated world.

9 CONSOLE MESSAGE: line 35: Injecting into main world again: this should fail.	9 CONSOLE MESSAGE: line 35: Injecting into main world again: this should fail.

10 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'".	10 CONSOLE ERROR: Refused to execute inline script because it violates the followin g Content Security Policy directive: "script-src 'self' 'unsafe-eval'". Either t he 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is r equired to enable inline execution.

11	11

12 This test ensures that scripts run in isolated worlds marked with their own Cont ent Security Policy aren't affected by the page's content security policy. Exten sions, for example, should be able to inject inline JavaScript (even though it's probably a bad idea to do so).	12 This test ensures that scripts run in isolated worlds marked with their own Cont ent Security Policy aren't affected by the page's content security policy. Exten sions, for example, should be able to inject inline JavaScript (even though it's probably a bad idea to do so).

OLD	NEW