Re: [w3ctag/design-reviews] Tabbed web apps (Issue #841)

Hi TAG,

Just giving this thread some updates on the developments on tabbed mode since February.

Acknowledging that TAG resolved this as "unsatisfied" based on not seeing a lot of value in the feature. We have posted additional justification above, and in the meantime, have pushed ahead with the feature.

* Tabbed Mode is [shipping in Chrome 126](https://groups.google.com/a/chromium.org/g/blink-dev/c/L6AfXU0-GOc/m/Y4SRkKUPAQAJ). At the present time, it will be ChromeOS only (see the discussion in that thread - this is due to resourcing, and we have noted that in principle this API can be applicable on all platforms).
* We have produced a comprehensive spec, currently incubating in the [manifest-incubations](https://wicg.github.io/manifest-incubations) repository. Here are direct spec links for the new [tabbed display mode](https://wicg.github.io/manifest-incubations/#dfn-tabbed) and the [tab_strip manifest member](https://wicg.github.io/manifest-incubations/#tab_strip-member).
* Tabbed mode was featured in the ChromeOS developer talk at [Google I/O last week](https://chromeos.dev/en/posts/io-2024#introducing-tabbed-pwa-mode). To coincide with this, [Figma](https://figma.com/) launched a PWA which works with tabbed mode on ChromeOS. There was some [press coverage](https://chromeunboxed.com/tabbed-pwas-for-chromebooks-will-be-a-game-changer-web-apps/) as well.

Cheers

Matt

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

Message ID: <w3ctag/design-reviews/issues/841/2128488662@github.com>