<
https://bugs.chromium.org/p/chromium/issues/detail?id=702760>
If we are only supporting this in secure contexts, we should rename the
test so that it has .https. in the filename which will cause it to be
loaded over https when run (e.g. in our CI). If there is general
agreement about restricting the feature to secure contexts, we should
additionally add a test that it doesn't work over http.
I can't imagine this would be controversial, but if it is we should at
least ensure that there's a copy of the test set up to run over https.