Re: [webauthn] Add a `hints` element for both `create` and `get`. (#1884)

I think apples implementation of hybrid is confusing people.  They assume
that a QR code is always required to start a hybrid flow.

It might be useful to explain the optimization that linking the phone
provides.

John B.

On Wed, May 3, 2023 at 6:23 PM Adam Langley via GitHub <sysbot+gh@w3.org>
wrote:

> > I would vote for two additional hints:
>
> > mechanism-selection: Indicates that the rp should show as "landing page"
> the list of all options.
>
> Does that apply to both create() and get() in your mind? I ask because
> we're rethinking that UI in Chrome for the get() case. (And I assume that
> you've some familiarity since you're using the Chromium terminology.)
>
> > cable-qrcode: Indicates that the rp should show as "landing page" the QR
> Code to initialize cable
>
> Are you thinking that this always shows a QR code, even if the user has a
> linked phone? Or is it more generally suggesting using a phone? The latter
> is what I was getting at with `non-security-key`. I don't like that name,
> but I hesitated to call it anything too specific. Maybe "smartphone" is a
> good answer?
>
> --
> GitHub Notification of comment by agl
> Please view or discuss this issue at
> https://github.com/w3c/webauthn/pull/1884#issuecomment-1533830255 using
> your GitHub account
>
>
> --
> Sent via github-notify-ml as configured in
> https://github.com/w3c/github-notify-ml-config
>
>