| tag | 9eba137a7fec5b572f2ffa214760f3d71314eb3b | |
|---|---|---|
| tagger | Adrià Vilanova Martínez <me@avm99963.com> | Sat Jan 10 00:34:55 2026 +0100 |
| object | e8108260641ff6c1f7ccdb2b606067d67d714597 |
v4.0.2 Changelog: https://gerrit.avm99963.com/plugins/gitiles/infinitegforums/+log/refs/tags/v4.0.1..refs/tags/v4.0.2
| commit | e8108260641ff6c1f7ccdb2b606067d67d714597 | [log] [tgz] |
|---|---|---|
| author | Adrià Vilanova Martínez <me@avm99963.com> | Fri Jan 09 23:58:44 2026 +0100 |
| committer | Adrià Vilanova Martínez <me@avm99963.com> | Sat Jan 10 00:20:58 2026 +0100 |
| tree | ab8bc8133eaf969560c515488e4b6ca401d042da | |
| parent | 85c745b3f3d0ba7c69140d766e5296eb3b34d4aa [diff] |
fix: fix loading options in Firefox In Firefox, we assumed that chrome.* APIs in a MV2 extension returned a Promise. However, this is not the case. This had the following consequences: - The extension stopped working completely in the forums. - Requests in the Community Console took a long time while the FetchProxy tried to detect whether some features were enabled (which failed) when trying to decide whether it should modify requests/responses. - The options page did not load nor save options. We fix this by using callbacks instead everywhere, since this is supported by both MV2 extensions in Firefox and MV3 extensions in Chromium. Bug: twpowertools:266 Change-Id: I799c84547fd73ee08e5a9bad669eaa456a6a6964
An extension which brings several enhancements to the Google Forums and the Community Console.
For a list of features/enhancements, check out the feature list doc.
This extension is being actively developed, and everyone is welcome to make feature requests, report issues and contribute code changes.
In order to make feature requests or report issues, please do so at the Monorail Issue Tracker:
To see a more exhaustive guide on how to contribute, and information on how to contribute code changes, please read the following doc:
Before releasing updates to the stable channel, the newest versions are uploaded to the beta channel so they can be tested by everyone who's interested. This is another way to contribute to the project, because beta testing can make us notice bugs before they reach the stable channel.
The beta channel for Chrome is available here.