-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ping in a thread followed by a non-ping makes the room go red->unread #25523
Closed
Labels
A-Notifications
A-Threads
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Critical
Prevents work, causes data loss and/or has no workaround
T-Defect
Comments
kittykat
added
S-Critical
Prevents work, causes data loss and/or has no workaround
A-Notifications
O-Occasional
Affects or can be seen by some users regularly or most users rarely
A-Threads
labels
Jun 8, 2023
I can't repro this now: the room stays red in the TAC as expected. |
wait, yes I can |
dbkr
added a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 11, 2024
This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523
4 tasks
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 12, 2024
* Fix highlights from threads disappearing on new messages This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523 * Add tests for the special notification behaviour in syncing
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 13, 2024
* Fix highlights from threads disappearing on new messages This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523 * Add tests for the special notification behaviour in syncing
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 20, 2024
* Fix highlights from threads disappearing on new messages This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523 * Add tests for the special notification behaviour in syncing
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 21, 2024
* Fix highlights from threads disappearing on new messages This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523 * Add tests for the special notification behaviour in syncing
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Mar 21, 2024
* Fix highlights from threads disappearing on new messages This changes interface of Room, so this is a BREAKING CHANGE. Correctly mirrors the logic we use for room notifications for thread notifications, ie. set only the total notifications count from the server if it's zero. I'm not delighted with this since it ends up with function on room whose contract is to do something frankly, deeply weird and unintuitive. However, this is the hack we use for room notifications and it, empirically, works well enough. To do better, we'd need much more complex logic to overlay notification counts for decrypted messages. Fixes element-hq/element-web#25523 * Add tests for the special notification behaviour in syncing * Correctly copy the room logic for reseting notifications We were always ignoring the highlight count, even for encrypted rooms, which was broken because we don't do the local calculation for unencrypted rooms.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Notifications
A-Threads
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Critical
Prevents work, causes data loss and/or has no workaround
T-Defect
Steps to reproduce
Outcome
What did you expect?
The room to stay red.
What happened instead?
It went from red at step 3 to unread (dot) at step 4.
Operating system
Windows 11
Application version
Element Nightly version: 0.0.1-nightly.2023060501 Olm version: 3.2.14
How did you install the app?
The Internet
Homeserver
t2l.io
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: