Thanks for the link and recommendation. I'll try to add a manual WPT for this feature following the example of the other web app tests. Is this a blocking issue?
On Monday, June 2, 2025 at 2:46:28 PM UTC-7 mike...@chromium.org wrote: > Multiple origins are possible, yeah: > > > https://web-platform-tests.org/writing-tests/server-features.html#tests-involving-multiple-origins > On 6/2/25 5:41 PM, 'Lu Huang' via blink-dev wrote: > > I thought about adding manual WPTs for this feature but it would require > serving from 2 different origins in the test environment. We did this in > browser tests. Is that also feasible in WPTs? > > On Monday, June 2, 2025 at 12:01:23 PM UTC-7 dan...@microsoft.com wrote: > >> > Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? >> >> >> > No >> >> I assume lack of WPTs is due to limitations of testing web app >> functionality in web-platform-tests. >> In the past it looks like manual WPTs have been added for certain PWA >> features in >> https://github.com/web-platform-tests/wpt/tree/master/appmanifest. Have >> you given any thought to adding any of that type of coverage for this? >> >> -- Dan >> >> On Wednesday, May 28, 2025 at 3:51:12 PM UTC-7 sligh...@chromium.org >> wrote: >> >>> I'm recused from this one, but grateful and happy to see it moving >>> forward. Godspeed! >>> >>> On Thursday, May 22, 2025 at 2:12:29 PM UTC-7 Chromestatus wrote: >>> >>>> Contact emails lu...@microsoft.com, luig...@microsoft.com, >>>> dmu...@chromium.org >>>> >>>> Explainer >>>> https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md >>>> >>>> >>>> Specification https://github.com/WICG/manifest-incubations/pull/113 >>>> >>>> Design docs >>>> >>>> https://docs.google.com/document/d/1-idhx8heajbPYl3cdXFVCjpIuf96cRa_DrRk6147ELI/edit?usp=sharing >>>> >>>> >>>> Summary >>>> >>>> Adds a "scope_extensions" web app manifest field that enables web apps >>>> to extend their scope to other origins. Example usage: { "name": >>>> "Example", >>>> "display": "standalone", "start_url": "/index.html", "scope_extensions": [ >>>> {"type" : "origin", "origin" : "https://example.com"} ] } This allows >>>> sites that control multiple subdomains and top level domains to be >>>> presented as a single web app. Requires listed origins to confirm >>>> association with the web app using a >>>> .well-known/web-app-origin-association >>>> configuration file. { "https://sample-app.com/": { "scope": "/" } } >>>> >>>> >>>> Blink component UI>Browser>WebAppInstalls >>>> <https://issues.chromium.org/issues?q=customfield1222907:%22UI%3EBrowser%3EWebAppInstalls%22> >>>> >>>> >>>> TAG review https://github.com/w3ctag/design-reviews/issues/875 >>>> >>>> TAG review status Issues addressed >>>> >>>> Origin Trial Name Web App Scope Extensions >>>> >>>> Chromium Trial Name WebAppScopeExtensions >>>> >>>> Origin Trial documentation link >>>> https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md >>>> >>>> >>>> WebFeature UseCounter name kWebAppManifestScopeExtensions >>>> >>>> Risks >>>> >>>> >>>> Interoperability and Compatibility >>>> >>>> *Gecko*: No signal ( >>>> https://github.com/mozilla/standards-positions/issues/904) >>>> >>>> *WebKit*: No signal ( >>>> https://github.com/WebKit/standards-positions/issues/265) >>>> >>>> *Web developers*: Positive >>>> https://github.com/WICG/manifest-incubations/issues/105 >>>> https://github.com/WICG/manifest-incubations/issues/46 >>>> >>>> *Other signals*: >>>> >>>> Ergonomics >>>> >>>> None. >>>> >>>> >>>> Activation >>>> >>>> None. >>>> >>>> >>>> WebView application risks >>>> >>>> Does this intent deprecate or change behavior of existing APIs, such >>>> that it has potentially high risk for Android WebView-based applications? >>>> >>>> None. Does not affect existing APIs. Developers must opt in with web >>>> app manifest. >>>> >>>> >>>> Debuggability >>>> >>>> DevTools Application pane will be the appropriate surface to add >>>> debugging support. Specifically, a section can be added to help >>>> troubleshoot the status of origin association validation. Additionally, >>>> edge://web-app-internals/ also have relevant information for debugging. >>>> >>>> >>>> Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, ChromeOS, Android, and Android WebView)? No >>>> >>>> Supported on Windows, MacOS, Linux, ChromeOS. Not supported on mobile >>>> platforms where app identity is implemented differently. >>>> >>>> >>>> Is this feature fully tested by web-platform-tests >>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>> ? No >>>> >>>> Flag name on about://flags >>>> about://flags/#enable-desktop-pwas-scope-extensions >>>> >>>> Finch feature name WebAppScopeExtensions >>>> >>>> Rollout plan Will ship enabled for all users >>>> >>>> Requires code in //chrome? False >>>> >>>> Tracking bug >>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1250011 >>>> >>>> Availability expectation Feature is available only in Chromium >>>> browsers for the foreseeable future. No signal from other vendors. >>>> >>>> Adoption expectation Feature is used by specific partner(s) to provide >>>> functionality within 12 months of launch in Chrome. >>>> >>>> Non-OSS dependencies >>>> >>>> Does the feature depend on any code or APIs outside the Chromium open >>>> source repository and its open-source dependencies to function? >>>> None. >>>> >>>> Sample links >>>> https://main-pwa-origin-2.glitch.me >>>> >>>> Estimated milestones >>>> Shipping on desktop 138 >>>> Origin trial desktop first 122 >>>> Origin trial desktop last 127 >>>> DevTrial on desktop 115 >>>> >>>> Anticipated spec changes >>>> >>>> Open questions about a feature may be a source of future web compat or >>>> interop issues. Please list open issues (e.g. links to known github issues >>>> in the project for the feature specification) whose resolution may >>>> introduce web compat/interop risk (e.g., changing to naming or structure >>>> of >>>> the API in a non-backward-compatible way). >>>> >>>> https://github.com/WICG/manifest-incubations/issues?q=is%3Aissue%20state%3Aopen%20label%3Ascope-extensions >>>> >>>> >>>> Link to entry on the Chrome Platform Status >>>> https://chromestatus.com/feature/5746537956114432?gate=5071001451233280 >>>> >>>> Links to previous Intent discussions Intent to Prototype: >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/-iySPmw8o34/m/oLgrCUQXAQAJ >>>> >>>> Ready for Trial: >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/OBZBZwS6qr0/m/VRySwd40AQAJ >>>> >>>> Intent to Experiment: >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/rGcbrUBB-5E >>>> >>>> >>>> This intent message was generated by Chrome Platform Status >>>> <https://chromestatus.com>. >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bdac7404-b53a-4482-a3ad-e922053eb830n%40chromium.org > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bdac7404-b53a-4482-a3ad-e922053eb830n%40chromium.org?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0a327e71-01f5-4cd4-b2be-30a023895d70n%40chromium.org.
