LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-iframe-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-iframe-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 | « no previous file | LayoutTests/http/tests/security/mixedContent/insecure-iframe-in-main-frame-allowed-expected.txt » ('j') | no next file with comments »

OLD	NEW
1 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame	1 frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame

2 main frame - didFinishDocumentLoadForFrame	2 main frame - didFinishDocumentLoadForFrame

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

4 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didStartProvisionalLoad ForFrame	4 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didStartProvisionalLoad ForFrame

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

6

7 didRunInsecureContent

8 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame	5 frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame

9 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didCommitLoadForFrame	6 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didCommitLoadForFrame

10 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didFinishDocumentLoadFo rFrame	7 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didFinishDocumentLoadFo rFrame

11 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didHandleOnloadEventsFo rFrame	8 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didHandleOnloadEventsFo rFrame

12 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame	9 frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame

13 main frame - didHandleOnloadEventsForFrame	10 main frame - didHandleOnloadEventsForFrame

14 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didFinishLoadForFrame	11 frame "<!--framePath //<!--frame0-->/<!--frame0-->-->" - didFinishLoadForFrame

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

16 main frame - didFinishLoadForFrame	13 main frame - didFinishLoadForFrame

17 This test loads a secure iframe that loads an insecure iframe. We should not g et a mixed content callback becase the main frame is HTTP and the grandchild ifr ame doesn't contaminate the child iframe's security origin with mixed content.	14 This test loads a secure iframe that loads an insecure iframe. We should not g et a mixed content callback becase the main frame is HTTP and the grandchild ifr ame doesn't contaminate the child iframe's security origin with mixed content.

18	15

19	16

OLD	NEW