Add non-secure webexposed listing tests |
|||
Issue descriptionThe tests in webexposed/ and http/tests/serviceworker/webexposed run in "secure" contexts (via file: and localhost exemptions, respectively) This means we don't have general tests enumerating the global exposed interfaces/methods/attributes in non-secure contexts, so e.g. we would not notice if a [SecureContext] attribute were added or - more worryingly - if it were dropped.
,
Jul 28 2017
That's cool (and close this off if you want); we do have scattered tests for "this interface should not exist in non-secure contexts". We might want to standardize on that in WPT, e.g. always have interfaces.html and interfaces.https.html for anything that has [SecureContext]
,
Oct 26 2017
,
Sep 20
|
|||
►
Sign in to add a comment |
|||
Comment 1 by rbyers@chromium.org
, Jul 28 2017Components: -Blink>Infra>Predictability