Revision b0f0ef9adb50765ea38be619015bb061d6a224b6 authored by Mustaq Ahmed on 27 June 2018, 15:33:46 UTC, committed by Blink WPT Bot on 27 June 2018, 15:42:47 UTC
With User Activation v2, activating a parent frame doesn't activate
its subframes. We fixed these two tests by sending the click to
subframes. This needed a workaround in auto-click.js because
the mutation observer there in doesn't seem to work when a button
element is added to a subframe.
Bug: 802371
Change-Id: I786668c87b802565e99ad16223cafc8ac1fd6296
Reviewed-on: https://chromium-review.googlesource.com/868323
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570778}
1 parent b44c265
nfc_insecure_context.html
<!DOCTYPE html>
<meta charset=utf-8>
<title>Web NFC Test: insecure context</title>
<link rel="author" title="Intel" href="http://www.intel.com"/>
<link rel="help" href="https://w3c.github.io/web-nfc/"/>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/nfc_help.js"></script>
<h2>Note</h2>
<ol>
<li>
Run test is an insecure context, e.g. http://example.com/
</li>
</ol>
<script>
"use strict";
test(t => {
assert_false(isSecureContext);
assert_false('nfc' in navigator);
}, 'navigator.nfc requires a secure context');
</script>
Computing file changes ...
