PWAsForFirefox 2.0.3

Added

• Support for opening URL input with Ctrl+L and Alt+D.

Fixed

• Fix typo in the RPM package link.
• Make Firefox Profiler button go to the tab strip area by default.
• Prevent crashing when requesting camera or microphone permission on macOS.
  You need to update/edit/re-create your web apps after installing the new native version, and maybe restart your computer.
  Note: The fix may not work. Please see #207 for details.

PWAsForFirefox 2.0.2

Added

• Tooltips to "Update manifest/icons" checkboxes to explain how they work (#195).

Fixed

• Fix hiding icon bar (#190).
• Fix runtime signing on macOS (#188, #198, thanks to @TitanNano).
• Fix uninstalling web apps on macOS.

PWAsForFirefox 2.0.1

Fixed

• A bug in GitHub Actions configuration that prevented v2.0.0 from being published.

PWAsForFirefox 2.0.0

Added

• Support for renaming web apps:
  Web apps can now be renamed on all operating systems without problems.

• Support for protocol handlers (#83):
  Protocol handlers (on web apps that register them) can be enabled from the extension web app settings.
  Enabled handlers are registered to the operating system and can be called from any other program.
  Note: This is not implemented yet on macOS.

• Support for changing theme color using meta tags (#96):
  Websites can now dynamically overwrite theme color using meta tags.
  This can be disabled in the runtime settings.

• Add support for automatic web app launching (#115):
  Any (enabled) URLs will be intercepted by the extension and re-launched in their web app windows.
  This feature can be enabled from the extension settings, and then configured for each web app.
  Note: Feature is experimental, may not work with all websites, and may impact performance.

• Add support for changing directories using run-time environment variables (#109).

• Add support for per-user installation on Windows (#129).

• Add options to prevent changing window icon and title (#167).

Changed

• System integration has been improved:
  Icon downloading and parsing are now more reliable.
  Protocol handlers are now supported.
  SVG icons are now supported.

• Some terminology has been changed to be more consistent:
  "Site" now represents a website available on the web, which you can install to your computer as a "web app" (PWA).
  "Site" is still used internally in some places and in connector requests to avoid breaking backward compatibility.

• Update checking has been changing (#114):
  Extension and native versions are now only "incompatible" when they differ in the major component.
  It is now possible to disable the update popup using a preference settings.show-update-popup (also available from the extension settings).
  The existing preference updates.native-version-check-disabled has been renamed to settings.disable-update-checking.

• Obtaining manifest URL from a content script has been improved.

• Profile name and web app ID are now displayed in the extension.

• Icon bar can now only be toggled if only Ctrl and Alt keys have been pressed (#177).

• All connector requests and responses are now documented.

Fixed

• Fix extension inputs:

  • Fix categories and keywords inputs.
  • Fix extension profile creation.

• Fix titlebar styling on Linux:

  • Window corners are now correctly rounded when necessary.
  • Native window controls are now correctly colored on darker theme colors.
  • Native window controls can now be forced even when using themes.

• Fix various things on macOS:

  • Fix macOS sharing widget.
  • Fix reopening web app after closing all windows (#42).
  • Prevent runtime Firefox from interfering with the normal one (#127).
  • Allow AdGuard to work with web apps (#131).
  • Improve web app titlebar style (#182).

Backward Incompatible Changes (Internal)

• The profile's default field has been removed. Profile is now a default if it has nil ULID. This does not affect users.
• Some connector requests have been changed. Extension needs to be updated to 2.0.0 to work correctly.
• Connector requests with optional params will now only process params that have been provided explicitly.

PWAsForFirefox 1.4.2

Fixed

• Fixes launch bug from the previous release (#157).
• Fixes PWAs not using CSD when they should.

PWAsForFirefox 1.4.1

Important

This release has a bug (#157) that prevents PWAs from being launched. This has been fixed in v1.4.2.

Fixed

• Partially fix disconnected windows (#79).
• Fix PWAs with Firefox 101.0 (#154, #155).

PWAsForFirefox 1.4.0

Added

• Support for bootstrapping manifest for GNU Guix (#88, thanks to @Kreyren):
  Users GNU Guix can now use native/manifest.scm to provide a temporary environment with the required dependencies to build the project.

• Support to build and install the project using cargo-make (#89, thanks to @Kreyren):
  Users can now just run makers install to automatically build and install the project.
  This is now a recommended way to install the project when building from the source.

• Keyboard shortcut (Ctrl+Shift+N) to open a default browser (#92):
  Users can now use a Ctrl+Shift+N shortcut (also available in the app menu) to open a preferred browser.
  Note: When using this shortcut for the first time, you may need to select your preferred browser using the displayed dialog.

• Support to open link in a new tab (#94):
  Added ability to force all links that should normally open in window or tab into a new tab.
  This can be useful in combination with close widget change (enabled by default) for a quicker page closing.

• Support to enable Wayland, XInput2 and XDG Portals (#101):
  Linux users can now enable Wayland, XInput2 and XDG Desktop Portals through the extension settings.

• Support for editing firefoxpwa.allowedDomains through settings page:
  Users can now edit firefoxpwa.allowedDomains through an input on the PWA settings page.

• Support for setting environment variables to the runtime:
  Custom environment variables for the Firefox runtime can now be passed using the variables key in the config file.

• Support for loading third-party UC scripts (#105):
  Loader of PWAsForFirefox UserChromeJS scripts will now attempt to load chrome/user/boot.jsm in the user profile.
  This can be used to load third-party UserChromeJS scripts and other modifications.

• Support for updating all installed PWAs (#107):
  Users can now trigger an update of all installed PWAs through the extension settings.
  This can also be used to automatically register all PWAs when transferring config from another device.

Changed

• Runtime and profile are now only patched when they need update (#53).
• Resume from crash functionality has been disabled by default (#86).
• Using close widget will now switch to the last tab with a scope URL if it exists (#94).
• Updated dependencies.

Fixed

• Incorrect site grouping on Wayland (#50).
• Incorrectly overwritten preferences.
• Broken widget icons.

---

You can download the extension from the Firefox Addon Store.

PWAsForFirefox 1.3.2

Important

According to Firefox Add-on Policies, exchanging information with the native application is considered a collection of personal data and must be disclosed in a privacy policy. Unfortunately, I wasn't aware of this specific policy so I didn't prepare any privacy policy for this addon.

This release adds the privacy policy to the license agreement during the installation process to comply with Firefox Add-on Policies. The whole privacy policy is also written below:

This extension exchanges personal data (current website and manifest URLs, as well as other PWA details) with the native program when the user initiates the PWA installation. This is necessary in order to correctly obtain and parse the Web Application Manifest and install the PWA. Data are stored on the computer as long as that PWA is installed. No personal data leave the computer or are sent to third parties.

As installed PWAs are running inside a Mozilla Firefox browser, you also need to agree to the Firefox Privacy Notice.

Fixed

• Added a privacy policy to comply with Firefox Add-on Policies.

---

You can download the extension from the Firefox Addon Store.

PWAsForFirefox 1.3.1

Fixed

• Incorrect registry key in MSI installer that caused the native program to fail (#98).
• Incorrect name in the firefox-pwa AUR package that prevented it from building (report).

---

You can download the extension from the Firefox Addon Store.

PWAsForFirefox 1.3.0

Important

This release has bugs (#98) that break the project on Windows and Arch-based Linux. This has been fixed in v1.3.1.

News

To avoid infringing Mozilla trademark policies and confusing users that this project is affiliated with Firefox and Mozilla, FirefoxPWA has been renamed to "Progressive Web Apps for Firefox" (shortly: "PWAsForFirefox" or "pwas-for-firefox"). Please use one of those names when referring to this project.

The project logo and all related icons have also been changed to use the CC0-licenced fox icon instead of the official Firefox logo.

The repository URL has been changed to https://github.com/filips123/PWAsForFirefox and the AMO URL has be changed to https://addons.mozilla.org/firefox/addon/pwas-for-firefox/. Existing packages and GitHub links will probably continue to work as GitHub provides automatic redirects from the old repository URL, but all links to AMO page need to be changed.

Note: Unfortunately, this is still not everything I planned for that bigger update. I will hopefully have time to release it this year...

Added

• Support for using this project on platforms without official Firefox support.
• Automatic pre-built DEB and RPM packages for Linux on ARM.

Changed

• Rebranded the project as Progressive Web Apps for Firefox (PWAsForFirefox).
• Improved the runtime installation step is reflect added support for additional platforms.

---

You can download the extension from the Firefox Addon Store, now with a different URL!