| commit | 72a4ea4f5d51e8b30acbff7f3f3940ca8a61926b | [log] [tgz] |
|---|---|---|
| author | Adrià Vilanova Martínez <me@avm99963.com> | Fri Feb 09 22:35:32 2024 +0100 |
| committer | Adrià Vilanova <me@avm99963.com> | Sat Feb 10 00:41:19 2024 +0000 |
| tree | 7cb84351ea4c01f98e5c1b84eff4d8f34c12b8ed | |
| parent | fbd73109a18067b49f64bb8129d175777d9e2d2c [diff] |
fix(flatten-threads): handle |#action=reply| correctly The action to open the reply editor is usually handled by the Community Console. With the flatten threads enabled, this sometimes opens a reply editor corresponding to a nested reply which when used wouldn't post the reply correctly. Thus, this CL adds logic to handle the |#action=reply| ourselves to open the reply editor adequately, as if the user clicked our own "Reply" button. This opens the reply editor corresponding to the parent reply (the first reply in the reply chain). Fixed: twpowertools:180 Change-Id: I1d734cfe0e28971939d292121ad6144f9e9f7a9a
- src/common/commonUtils.js[diff]
- src/contentScripts/communityConsole/flattenThreads/components/ReplyButton.js[diff]
- src/contentScripts/communityConsole/flattenThreads/replyActionHandler.js[Added - diff]
- src/contentScripts/communityConsole/start.js[diff]
- src/contentScripts/communityConsole/utils/common.js[diff]
- .github/
- cws/
- docs/
- playbooks/
- roles/
- src/
- templates/
- tools/
- .babelrc
- .clang-format
- .editorconfig
- .eslintrc.json
- .gitignore
- .gitreview
- .zuul.yaml
- i18n-config.toml
- jest.config.js
- LICENSE
- lit-localize.json
- Makefile
- OWNERS
- package-lock.json
- package.json
- README.md
- renovate.json
- tagRelease.bash
- webpack.config.js
TW Power Tools
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.