Yes, there will be a separate intent for the change to require a secure
context. We're making this change first since it's not expected to break
anything while the secure context change will break API access from
non-secure contexts.

I put together some notes on my current plans in Securing Gamepad API in
Chrome
<https://docs.google.com/document/d/1Dj_7EpT9ttnI96BuNXtLEJkHEq0orHgoLeYaOBz9xsU/edit#>
and
will update that if anything changes.

- Matt

On Wed, Apr 27, 2022 at 1:45 AM Artur Janc <[email protected]> wrote:

> Hey folks,
>
> Can you share a little bit about your future plans to restrict the use of
> Gamepad API? Implementing Permissions Policy integration sounds good, but
> without the restriction to secure contexts and changing the default
> allowlist to 'self' it doesn't seem like we're substantially locking down
> the API. Are you planning to do this in subsequent intents?
>
> Thanks!
> -Artur
> On Tuesday, April 26, 2022 at 8:10:17 PM UTC+2 Matt Reynolds wrote:
>
>> Chrome 103
>>
>> On Mon, Apr 25, 2022 at 7:33 AM jmedley via Chromestatus <
>> [email protected]> wrote:
>>
>>> Which version of Chrome are you hoping to ship this in?
>>>
>>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/00000000000039989e05dd7b742d%40google.com
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/00000000000039989e05dd7b742d%40google.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BqnoudiT56vqcSy0m581FKq-VQ6FQPdhr7xaVvDxCbHK5gbbw%40mail.gmail.com.

Reply via email to