Re: [w3ctag/design-reviews] Declarative Link Capturing (#589)

Thanks for your comments @alice .

I or @alancutter will update the explainer in response. I think we can provide specific use cases for each one.

Also note that we're planning to implement these `capture_links` enums one-by-one, starting with `new_client` and `existing_client_navigate`. So I just put up a big list, but we can implement them (and spec them) as the need arises, rather than speculatively assuming there's a need for all of them.

> Also, it would be helpful to have an explanation of how this would be used in the context of a mobile OS which typically has one window per application. How would that interact with the `new-client` option?

We should think of this entire feature as a hint to the user agent. It doesn't *have* to do what you ask. Browsers are (generally) allowed to close any window / tab whenever it wants, and routinely do. So even if you ask for `new_client`, the mobile browser can just implement it as `existing_client_navigate`, destroying your existing context, which is not very acceptable on desktop but quite normal on mobile. We'll say that in the explainer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/589#issuecomment-786437346