Re: [w3c/manifest] Add Manifest option for specifying browser app picker behavior (#764)

>> -Some PWAs may want the browser to always show the app picker for link clicks into their PWA, to give the user the option of which app to open the link with.
> Could you clarify a case where an app might want this behaviour?

Twitter may want the user to be able to install their PWA without link clicks always opening in the PWA. They may want the user to be able to decide whether it opens in the browser, in the android app or in the PWA. 

> To my mind, this feels like the behaviour most apps would want.

Agreed, but only if the PWA is the primary experience

> Are there any other examples aside from OAuth providers that might want this exclusion behaviour?

That's the main example.

> As per the thread here, is there any reason to avoid:
> link_capturing_preference: {
>     "/": "always",
>    "/v5.5/dialog/oauth": "never"
> }
> and use the list of objects syntax?

No, I think your suggestion is better :) 

> Everything is a preference, even scope - they browser can always override behavior - or not implement it. Not sure why we need the _preference

Good question. Thinking more about it:
1) If the PWA says don't capture, I think it should never be captured
2) If the PWA says ask the user, I think it should always ask the user (user can save the preference)
3) If the PWA says always open, I think it's up to the browser to decide but we recommend always opening

For (3) it is really a hint by the app but I think the user agent is still in the best place to decide what's best for the user.

> @dominickng's comments makes this more sounds like a whitelist or a blacklist.

We thought about it being a blacklist but I think this behavior is more flexible and more aligned with a platform like Android which effectively provides all of these options.

> FYI, ask_user in other spec like Permissions we call this prompt - actually there we used granted, denied and prompt which seems to fill well here as well

I'm flexible with terminology. 'prompt' does seem better than 'ask_user'. granted/denied I'm not so sure about.

> Would making it a list of exclusions under "scope" still satisfy the need?

It would solve the oauth problem but I don't think it provides the flexibility to tell the browser the apps preference with regard to capturing. Some apps will /want/ the user to be in control. Other apps will /want/ to always handle links themselves if possible.

Possibly it makes sense to break it out into 2 different features. link_capturing_excluded and a separate option which is a preference of how to handle captures. The original proposal seems a bit cleaner to me though.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/764#issuecomment-488910137