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
I understand there are issues and limitations with Firefox containers/Multi-Account Containers impacting PWA. I have found a work around using the Open external links in a container add-on. This will launch the PWA directly into the container of your choice. The only issue is the PWA start_url validation prevents you from using the syntax needed for this add-on and gives the error, "Start URL needs to be a valid URL".
I have tested this work around by editing the PWA config.json directly and can confirm that it does work.
Proposed Solution
Could you remove the validation for start_url?
The text was updated successfully, but these errors were encountered:
I can try to turn it into warning or someting similar. But I'm not sure if it will work properly, as I think there is also some validation in the manifest that requires start URL to be in the scope.
Problem Description
I understand there are issues and limitations with Firefox containers/Multi-Account Containers impacting PWA. I have found a work around using the Open external links in a container add-on. This will launch the PWA directly into the container of your choice. The only issue is the PWA start_url validation prevents you from using the syntax needed for this add-on and gives the error, "Start URL needs to be a valid URL".
I have tested this work around by editing the PWA config.json directly and can confirm that it does work.
Proposed Solution
Could you remove the validation for start_url?
The text was updated successfully, but these errors were encountered: