You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This allows for the WordPress admin to be installed to the homescreen separately for ease of access, separately from installing the frontend to the homescreen. The PWA plugin already is registering a service worker in the admin scope, but the admin is not installable as a separate PWA because there is no admin-specific web app manifest. This is what was proposed in #295 as mentioned in WordPress/gutenberg#33102 (comment).
Only one service worker can be registered for a given scope at a time. Since the purpose of the PWA plugin's service worker is to be extensible via a WP_Scripts-esque API, it is preferable to use instead of the service worker shim in Gutenberg which is required to trigger the add-to-homescreen prompt.
In Gutenberg 11.1, experimental support for admin PWA was introduced: WordPress/gutenberg#33102, WordPress/gutenberg#33310, WordPress/gutenberg#33216.
This allows for the WordPress admin to be installed to the homescreen separately for ease of access, separately from installing the frontend to the homescreen. The PWA plugin already is registering a service worker in the admin scope, but the admin is not installable as a separate PWA because there is no admin-specific web app manifest. This is what was proposed in #295 as mentioned in WordPress/gutenberg#33102 (comment).
Only one service worker can be registered for a given scope at a time. Since the purpose of the PWA plugin's service worker is to be extensible via a
WP_Scripts
-esque API, it is preferable to use instead of the service worker shim in Gutenberg which is required to trigger the add-to-homescreen prompt.The text was updated successfully, but these errors were encountered: