-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for scope_extensions
in PWABuilder
#4668
Comments
scope_extensions
on PWABuilderscope_extensions
in PWABuilder
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
3 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
Tell us about your feature idea
We are currently running an OT for
scope_extensions
, a feature that is expected to land in Chromium 127. As the best up-to-date tool for PWA packaging and functionality, we want PWABuilder to support this feature. This is important for partners that require an expanded scope for use cases like multiple TLDs.Do you have an implementation or a solution in mind?
This should be added to the manifest editor in PWABuilder, providing an option to add multiple domains to the generated manifest file.
After this is added, support for
appURIHandler
should be removed.Have you considered any alternatives?
No response
The text was updated successfully, but these errors were encountered: