Add a capability for receiving sticky events#157
Merged
Conversation
In the future when we try to implement the active pushing of the sticky event map to the widget in clients, I believe we will want this to be gated behind a capability. By adding the capability now, we allow widgets to start requesting the capability already and benefit from the improved delivery guarantees of sticky events later for free.
|
toger5
reviewed
Jan 16, 2026
Contributor
toger5
left a comment
toger5
left a comment
There was a problem hiding this comment.
We also still need to add m.rtc.member events.
It did not fit into this PR:
element-hq/element-call#3675 (comment)
But here it makes a lot of sense to add this?
Member
Author
|
This is a matrix-widget-api PR. I will be changing that in element-call though. |
Contributor
|
Ugh I am blind. |
toger5
approved these changes
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the future when we try to implement the active pushing of the sticky event map to the widget in clients, I believe we will want this to be gated behind a capability. By adding the capability now, we allow widgets to start requesting the capability already and benefit from the improved delivery guarantees of sticky events later for free.