Gitiles
Code Review Sign In
gerrit.avm99963.com / infinitegforums / 61f782f23caa9496e1a3f81e25986fb7de37bf26
commit61f782f23caa9496e1a3f81e25986fb7de37bf26[log] [tgz]
authorAdrià Vilanova <me@avm99963.com>Fri May 31 22:57:24 2024 +0000
committerAdrià Vilanova Martínez <me@avm99963.com>Sat Jun 01 01:53:30 2024 +0200
treef0ee64186eea402aee55959ccf9ea90693985b8b
parent230664fb12cc181aea471717f015d983711c24de [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
16 files changed
tree: f0ee64186eea402aee55959ccf9ea90693985b8b
  1. .github/
  2. cws/
  3. docs/
  4. playbooks/
  5. roles/
  6. src/
  7. templates/
  8. tools/
  9. .babelrc
  10. .clang-format
  11. .editorconfig
  12. .gitignore
  13. .gitreview
  14. .prettierrc.yaml
  15. .zuul.yaml
  16. eslint.config.js
  17. jest.config.js
  18. LICENSE
  19. lit-localize.json
  20. Makefile
  21. OWNERS
  22. package.json
  23. pnpm-lock.yaml
  24. README.md
  25. renovate.json
  26. tagRelease.bash
  27. tsconfig.json
  28. webpack.config.js
README.md

TW Power Tools

Available in the Chrome Web Store Get the add-on for Firefox

Build status Translation status

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.

Information for contributors

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:

Beta channel

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.