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

@wraiford : Based on my understanding, Chrome on Android lets you add to homescreen and the result will be based on "display". If it's "display": "browser" (or nothing), it will just act like a normal browser shortcut, opening a new tab in the Chrome browser. If it's "display": "minimal-ui" or "standalone", it will create its own window. This seems aligned with the spec. I suspect you are installing an app with "display": "minimal-ui" or "standalone".

This is fairly orthogonal to what is being proposed here, which is a separate tabbed mode inside a standalone app window. (That is the point being made in the paragraph you quoted, which is to emphasise that "display": "browser" is not appropriate for triggering the standalone tabbed mode.)

> It is my understanding that the "tabbed application" is only being currently implemented on the desktop. Is that correct?

That is currently correct for Chrome, though this GitHub is in the W3C which is browser-neutral, and I can't speak for other browsers. There is nothing stopping another browser (or Chrome in the future) from implementing standalone tabbed mode on mobile, though more UX research is probably required.

> 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?

Again, this isn't a Chrome issue tracker so I don't want to get too far into discussing Chrome bugs here. You can always file a bug at https://crbug.new. I don't think having tabbed application mode on mobile will help what you want. (It would mean the apps you install are getting their own mini tab interface, and only if they request "display": "tabbed".) Sites with "display": "browser" should already be doing what you want. Sites with "display": "minimal-ui" or "standalone" should open in their own window, but as @EiraGe stated, there is a pull-down notification that lets you open them in Chrome. It sounds as though things are working as intended on the Chrome side.

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

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