Re: [w3c/manifest] Add a "tabbed application" mode (#737)

> Because display: browser already has a specific meaning. "Opens the web application using the platform-specific convention for opening hyperlinks in the user agent (e.g., in a browser tab or a new window)." While user agents can do whatever they want regarding UI, it would clearly be a pretty big subversion of developer expectations if "display: browser" suddenly meant "run in a separate application-specific window with no browser affordances, but a tabbed document interface".

This is entirely what does NOT happen on Chrome mobile (Android). With either `display: "browser"` or no `display` setting at all, Chrome mobile adds a link that looks like it's going to open the browser - but doesn't. It opens a single-tabbed application - exactly what the above quote says would be a "pretty big subversion". And he/she is correct in my particular case.

As such, it looks like I can't use the tabs in an offline manner for any PWAs at all. Firefox for Android does not respect the service worker properly and starts giving connection errors. And Chrome mobile does indeed work offline, but it only shows one tab without the ability to even open in the Chrome Mobile browser proper. I do see that the desktop does at least allow "Open in Chrome" which would totally be fine in the mobile if not slightly annoying. But a large difference between the desktop app is that it is easier to drag bookmarks to the desktop (screen), whereas this functionality exists on mobile **only as the Add to Home Screen functionality**. So I can't just add a bookmark to my Android's "desktop" home screen to even work around the lack of tab functionality. 

It is my understanding that the "tabbed application" is only being currently implemented on the desktop. Is that correct? Could someone point me to an issue or where to create a new issue with the Chrome mobile PWA team to at least request the ability to "Open in Chrome" as a stop gap until tabbed functionality gets extended to mobile?

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

Message ID: <w3c/manifest/issues/737/1216973670@github.com>