LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt - Issue 18104009: Mixed content iframe checks should use top

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/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt

Issue 18104009: Mixed content iframe checks should use top (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Drop back to canDisplay Created 7 years, 5 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/mixedContent/insecure-iframe-in-iframe-expected.txt ('k') | LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-blocked-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 main frame - didStartProvisionalLoadForFrame	1 main frame - didStartProvisionalLoadForFrame

2 main frame - didFinishDocumentLoadForFrame	2 main frame - didFinishDocumentLoadForFrame

3 main frame - didHandleOnloadEventsForFrame	3 main frame - didHandleOnloadEventsForFrame

4 main frame - didFinishLoadForFrame	4 main frame - didFinishLoadForFrame

5 main frame - didCommitLoadForFrame	5 main frame - didCommitLoadForFrame

6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame	6 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame

7 CONSOLE MESSAGE: line 9: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-insecure-iframe.html ran insecure content from http://127 .0.0.1:8080/security/mixedContent/resources/boring.html.	7 CONSOLE MESSAGE: line 9: The page at https://127.0.0.1:8443/security/mixedConten t/resources/frame-with-insecure-iframe.html displayed insecure content from http ://127.0.0.1:8080/security/mixedContent/resources/boring.html.

8	8

9 didRunInsecureContent	9 didDisplayInsecureContent

10 main frame - didFinishDocumentLoadForFrame	10 main frame - didFinishDocumentLoadForFrame

11 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame	11 frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame

12 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame	12 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame

13 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame	13 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame

14 main frame - didHandleOnloadEventsForFrame	14 main frame - didHandleOnloadEventsForFrame

15 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame	15 frame "<!--framePath //<!--frame0-->-->" - didFinishLoadForFrame

16 main frame - didFinishLoadForFrame	16 main frame - didFinishLoadForFrame

17 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback even though we've set the preference to block this, because w e've overriden the preference via a web permission client callback.	17 This test opens a window that loads an insecure iframe. We should trigger a mixe d content callback even though we've set the preference to block this, because w e've overriden the preference via a web permission client callback.

OLD	NEW