Re: [webauthn] Deprecate Authenticator Attachment in favor of Hints (#2383)

> Current hints are an ordered list. In reality most OS just use the first item to optimize the UX and everything else is clubbed together. It might make sense to move away from ordered list to a single hint notion - where RPs get to optimize just the first screen.

Initially when hints were designed, I had assumed that it will be used for multiple features with each having multiple options and RP will choose one of the options for each feature supported. 

For example, let's say there were two features - Feature_1 (with options A,B,C) and Feature_2 (With Options P,Q,R)

I thought RP can choose one of values from inside from each set. For example, these are below valid options.
- A, P
- A, Q
- B, P
- Q, C
etc. 

In my understanding, RP sending multiple options from same feature was not the initial design. So following options are not valid ones.  
- A, B
- B, C, A

I had not thought of hints being only restricted to transports hints only as one and only one feature. 

AFAIK, every platform uses the first applicable hint for transport and ignores the rest of values. If that is the practical implementation truth and design intention and we all agree, we should clarify the spec. 

-- 
GitHub Notification of comment by akshayku
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/2383#issuecomment-4243224220 using your GitHub account


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

Received on Tuesday, 14 April 2026 10:36:40 UTC