Re: [battery] Assess compatibility risk of using [SecureContext] (#15)

This is one of, I believe, two APIs on the platform which do explicit secure context checks instead of using [SecureContext]. This is causing minor integration problems for other features like prerendering.

I think your argument in the OP indicates it'd be *better* to use [SecureContext]. That is, non-secure HTTP pages would be better off going down the "this browser does not suppport the API" path, and treating it similar to they do Firefox and Safari, instead of calling the API and getting surprised by a rejected promise.

-- 
GitHub Notification of comment by domenic
Please view or discuss this issue at https://github.com/w3c/battery/issues/15#issuecomment-786122936 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 25 February 2021 18:50:05 UTC