Contact emails [email protected], [email protected], [email protected]
Explainer https://github.com/WICG/manifest-incubations/blob/gh-pages/manifest-scope-improvements/scope-inclusions-and-exclusions.md Specification No information provided Summary Web developers can use scope inclusions and exclusions to define which URLs belong to an installed web app using URL patterns. This helps apps include non-contiguous or parameterized routes and exclude specific paths, so only intended URLs open in the app window. Blink component UI>Browser>WebAppInstalls Web Feature ID manifest Motivation The existing Web App Manifest scope member supports only a single URL prefix. Real-world web apps often need to exclude non-app pages—such as sign-out, help, download, or API routes—or include non-contiguous and parameterized app routes. Without finer control, developers must capture unintended URLs, restructure their sites, or avoid scope-dependent capabilities such as navigation capturing. This proposal adds origin-owned, backward-compatible scope inclusions and exclusions. Initial public proposal https://github.com/WICG/manifest-incubations/issues/105 Goals for experimentation None Requires code in //chrome? True Tracking bug https://issues.chromium.org/issues/543924642 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5184195986063360?gate=5097475227648000 This intent message was generated by Chrome Platform Status. -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a7caeff.dca7d4cf.3319e9.0868.GAE%40google.com.
