Fwd: Intent to Implement and Ship: `CredentialsContainer::preventSilentAccess` in Credential Management API

this is a change going into 
https://w3c.github.io/webappsec-credential-management/ per our request...

On Friday, May 19, 2017 at 5:27:36 AM UTC-7, Jan Wilken wrote:
>
> Contact emails
>
> jdoe...@chromium.org <javascript:>, vas...@chromium.org <javascript:>
>
>  
>
> Specification
>
> https://w3c.github.io/webappsec-credential-management/
>
> Summary
>
> This intent renames CredentialsContainer::requireUserMediation to 
> CredentialsContainer::preventSilentAccess in the Credential Management 
> API.
>
>   
>
> Motivation
>
> The WebAuthn API was rewritten in https://github.com/w3c/webauthn/pull/384 
> to extend the Credential Manager API. 
>
> One of the issues raised is that "requireUserMediation" is a poor name for 
> their use case. Thus this new name is introduced.
>
> Please see the correponding GitHub issue for more details: 
> https://github.com/w3c/webappsec-credential-management/issues/74
>
>
> Usage information
>
> Usage of the Credential Manager API is low in general: 
> https://www.chromestatus.com/metrics/feature/popularity#CredentialManagerGet
>
>
> Interoperability and Compatibility Risk
>
> Low risk, since overall usage is low and no other browser has shipped the 
> Credential Manager API yet.
>
>  
>
> Alternative implementation suggestion for web developers
>
> Instead of using requireUserMediation web developers should use 
> preventSilentAccess instead. 
>
>  
>
> OWP launch tracking bug
>
> *http://crbug.com/724464 <http://crbug.com/724464>*
>
>
> Entry on the feature dashboard
>
> *https://www.chromestatus.com/feature/4781762488041472*
> <https://www.chromestatus.com/feature/4781762488041472>
>
>  
>
> Requesting approval to remove requireUserMediation?
>
> No, complete removal is planned for M62.
>
>  
>
> Requesting approval to ship preventSilentAccess?
>
> Yes.
>