chromium/src
0
Fork 0
Code Activity

De-flake cross-domain-iframe.sub.html

Browse Source 
If this doesn't deflake the test, then I suspect that there is an issue
on some bots with the cross-origin domain name being resolved. On my
machine, the origin of the iframe was www1.web-platform.test:8001, and
if the machine doesn't have the custom wpt domains configured, then the
test will produce a white screen just like the flaky failures.

Bug: 1091270
Change-Id: I4db90275632166b01a53fc6a7fa54c006c4c14d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2236740
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#776976}
This commit is contained in:
Joey Arhar
2020-06-10 16:50:16 +00:00
committed by Commit Bot
parent fe59f07f74
commit b447a3ac5e
1 changed files with 6 additions and 1 deletions

7
third_party/blink/web_tests/external/wpt/html/rendering/replaced-elements/embedded-content/cross-domain-iframe.sub.html vendored

@ -1,6 +1,11 @@
<!doctype html>
<html class="reftest-wait">
<title>Rendering of iframe element with src attribute from another domain</title>
<link rel="match" href="cross-domain-iframe.sub-ref.html">
<link rel="help" href="https://html.spec.whatwg.org/multipage/rendering.html#embedded-content-rendering-rules">
<meta name="assert" content="Checks that iframe content is correctly rendered even if it is retrieved from a different domain.">
<iframe src="http://{{domains[www1]}}:{{ports[http][0]}}/images/green.png"></iframe>
<iframe id=myframe src="http://{{domains[www1]}}:{{ports[http][0]}}/images/green.png"></iframe>
<script>
myframe.onload = () => document.documentElement.classList.remove('reftest-wait');
</script>
</html>