New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 897314 link

Starred by 7 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Tabbed application mode for PWAs

Project Member Reported by dxie@google.com, Oct 19

Issue description


 
Labels: Proj-Fugu
Labels: Type-Feature
Owner: pcovell@chromium.org
Hey Paul, can you give input on how important this is? 
Doesn't this already exist? Or is this different from the manifest property?
Cc: pcovell@chromium.org
Labels: Pri-1
Owner: mgiuca@chromium.org
Status: Assigned (was: Untriaged)
waiting on additional feedback.
Cc: dominickn@chromium.org
Components: UI>Browser>WebAppInstalls
Labels: OS-Chrome OS-Linux OS-Mac OS-Windows
Summary: Tabbed application mode for PWAs (was: `display: browser` (tabbed mode))
GitHub issue:
https://github.com/w3c/manifest/issues/737

Discussion doc (Google only):
https://docs.google.com/document/d/1wchuU6uZAt10LYYL4U0GmI4lndwdkoMdvXKLiZkJ5Aw/edit

#4:
> Doesn't this already exist? Or is this different from the manifest property?

There's been some confusion because this feature keeps being labeled as "display: browser", which does already exist and has a separate meaning (specifically, that the app is opened in a regular browser tab).

This feature is about having a standalone app window with multiple tabs (containing separate documents inside the app scope) inside it.

Regardless of how we design this, the name of the feature proposal should not be named after a proposed solution, since that unnecessarily pigeonholes us into a particular solution.
Labels: Target-78 M-81
Cc: mgiuca@chromium.org
Labels: -OS-Linux -Pri-1 Pri-2
Owner: alancutter@chromium.org

Sign in to add a comment