Re: Presentation API in non secure contexts from mark a. foltz on 2017-01-23 (public-webappsec@w3.org from January 2017)

From: mark a. foltz <mfoltz@google.com>
Date: Mon, 23 Jan 2017 13:17:15 -0800
To: Richard Barnes <rbarnes@mozilla.com>
Cc: Francois Daoust <fd@w3.org>, WebAppSec WG <public-webappsec@w3.org>, public-web-security@w3.org, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
Message-ID: <CALgg+HEHdG2qpjkkhAz81D5nkUgCjn7Qy+X6g1g+DbA8XRWFMA@mail.gmail.com>

On Mon, Jan 23, 2017 at 9:06 AM, Richard Barnes <rbarnes@mozilla.com> wrote:

> What is the rationale for why this API needs to be available to non-secure
> contexts?
>

At the time the group considered this, it was judged to not be a powerful
feature.
We have asked for an updated rubric for evaluating what is a powerful
feature, and have not yet received a reply.

m.

Received on Monday, 23 January 2017 21:18:09 UTC