tag | f0046ed516e55121364f5313d2f4b31bc20fe3ff | |
---|---|---|
tagger | Adrià Vilanova Martínez <me@avm99963.com> | Sat Jun 01 01:54:27 2024 +0200 |
object | 61f782f23caa9496e1a3f81e25986fb7de37bf26 |
v3.0.0 Changelog: https://gerrit.avm99963.com/plugins/gitiles/infinitegforums/+log/refs/tags/v2.9.0..refs/tags/v3.0.0
commit | 61f782f23caa9496e1a3f81e25986fb7de37bf26 | [log] [tgz] |
---|---|---|
author | Adrià Vilanova <me@avm99963.com> | Fri May 31 22:57:24 2024 +0000 |
committer | Adrià Vilanova Martínez <me@avm99963.com> | Sat Jun 01 01:53:30 2024 +0200 |
tree | f0ee64186eea402aee55959ccf9ea90693985b8b | |
parent | 230664fb12cc181aea471717f015d983711c24de [diff] |
Revert "feat!: remove features related to the old thread page view" This reverts commit 879d44aef99524c84719d91c628e772fba9335cb. Reason for revert: It turns out the old reply editor can still be used in the new thread page view by pressing the "R" key, and this can/will make the CC communicate with the draft endpoints to save/retrieve information. Apart from this, some PEs were using the "old thread page" option as well, even if it doesn't load all replies. Finally, this revert also contains some changes to the modifications to the data startup object so they work correctly (since now we have to use StartupDataStorage, otherwise changes might not be saved). Bug: twpowertools:124 Change-Id: Ie8153b9c8ef150b2417cb19b73bde0a5593876e2
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.