A tool to install, manage and use Progressive Web Apps (PWAs) in Mozilla Firefox
In versions 2.7.0 and 2.7.1, the extension does not display the installation instructions properly. This issue is tracked as #368 and will be fixed as soon as possible. Affected versions have been disabled from AMO. If you have this issue, please downgrade the extension to 2.6.2 until this is properly fixed. Version 2.7.2 has been released with a fix. You should be able to quickly update to it by searching for updates on about:addons.
Prevented syncing some preferences and reset problematic ones:
Web app profiles now prevent syncing certain preferences that are commonly set to different values in web apps, as well as those known to cause problems. If you know what you are doing and still want to sync one of those preferences, you can enable them back using the services.sync.prefs.sync. control preferences. In the future, we could try to implement a different syncing "channel" just for web apps.
Additionally, the preferences known to cause problems were reset. Those preferences currently cannot be changed by users as they will be reset on every web app startup. This might be removed in the future, once enough users have had those preferences reset.
This is another attempt in fixing issues https://github.com/filips123/PWAsForFirefox/issues/253 and https://github.com/filips123/PWAsForFirefox/issues/349.
Added missing $pkgdir in the destination path of AUR package.
In versions 2.7.0 and 2.7.1, the extension does not display the installation instructions properly. This issue is tracked as #368 and will be fixed as soon as possible. Affected versions have been disabled from AMO. If you have this issue, please downgrade the extension to 2.6.2 until this is properly fixed. Version 2.7.2 has been released with a fix. You should be able to quickly update to it by searching for updates on about:addons.
Support for wildcards when matching the allowed domains list (#328):
A wildcard * can now be used in an allowed domain list to match zero or more characters. A wildcard can be escaped by using \*.
For example, to match domains such as mail.google.com, calendar.google.com and google.com, set the allowed domains list to *.google.com,google.com.
Support for excluding URLs with regex for automatic launching (#296): Specific URLs can now be excluded from the automatic web app launching in the extension settings. Any URLs that match the provided regex will not be launched as a web app. This only has effect when web app launching is enabled.
AppStream metadata for Linux packages: This metadata should be appropriately included in packages and repositories when packaging/distributing the project on Linux. This should help improve the display of packages on Linux software stores such as GNOME Software and KDE Discover.
Disabled new tab feeds and configure homepage (#253, #349): This might be related to unexpected opening of websites and images while using web apps, reported in issues #253 and #349.
Fixed an incorrect CSS selector on the preferences page.
Fixed incorrect Gentoo installation instructions.
A new documentation website is in progress. I will appreciate it if you read and participate in a discussion to help improve it.
There are two new options for each web app in the extension, "Launch this web app on system login" and "Launch this web app on browser launch", to determine if the web app should be automatically launched when the user logs in to the system and when the Firefox browser is launched.
firefoxpwa.openInExistingWindow preference has been replaced to allow further configuration of how the web app should be launched when it is already opened.
It is now possible to open a new window (default behavior), open a new tab in the existing window (behavior of previous preference), replace an existing tab, or just focus the window.Web apps from the same profile should no longer be merged on Linux (#80): This release adds required code changes on the PWAsForFirefox part to fix the long-standing issue #80. The fix also requires some changes on the Firefox part, which will be released in Firefox 112.
Link targets will no longer change when the out-of-scope preference changes.
Custom web app icons should now be applied properly.
Mute toolbar widget icon should now display properly.
Installing extensions should now work properly (#297).
Extensions widget should now work properly (#308).
Permissions for runtime autoconfig files have been fixed (#311).
The extension now requires the notifications permission in order to display a notification on updates.
Installation instructions for PortableApps.com in the extension: The extension will now also display installation instructions for the PortableApps.com package in the setup wizard.
Support for setting custom icons (#128):
You can now set custom icon URLs when installing or updating web apps.
This can be done using the extension or using the --icon-url console argument.
Support for profile templates (#219):
There is an option in the extension settings to choose the default profile template.
It is also possible to use a different template directory when creating a specific profile.
The template directory can also be provided using the --template console argument.
Contents of the specified template directory will be copied to new profiles when they are created.
winget installation step in the extension (#262, thanks to @louis993546).help.html file of the package.