Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(93)

Side by Side Diff: third_party/WebKit/LayoutTests/external/wpt/fullscreen/api/element-ready-check-allowed-cross-origin-manual.sub.html

Issue 2898503002: Reenable feature policy control over fullscreen (Closed)
Patch Set: Reworking tests a bit Created 3 years, 4 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
OLDNEW
(Empty)
1 <!DOCTYPE html>
2 <title>Element ready check with fullscreen allowed</title>
3 <script src="/resources/testharness.js"></script>
4 <script src="/resources/testharnessreport.js"></script>
5 <script src="../trusted-click.js"></script>
6 <iframe src="http://{{domains[www1]}}:{{ports[http][0]}}/fullscreen/api/resource s/attempt-fullscreen.html" name="cross-origin-allowed" allowfullscreen></iframe>
7 <script>
8
9 async_test((t) => {
10 // When a message is received from a child frame, ensure that the report
11 // matches the expectations.
12 window.addEventListener('message', t.step_func(e => {
13 if (e.data.report && e.data.report.api == "fullscreen") {
14 assert_equals(e.data.report.result, true,
15 e.data.report.frame + " frame did enter fullscreen");
16 t.done();
17 }
18 }));
19
20 // Trigger the child frame to report as soon as its content is loaded.
21 var elem = document.querySelector('iframe');
22 elem.addEventListener('load', () => {
23 trusted_click(t, () => {
24 elem.contentWindow.postMessage({"action": "report"}, "*");
25 }, document.body);
26 });
27 });
28 </script>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698