widget-api: Implement driver readStickyEvents
#31872
Draft
+50
−1
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.
Depends on: matrix-org/matrix-widget-api#161
Implements a new functionality to push pre-existing sticky state when a widget is loaded, to give it an accurate view of the state.
This give the current sticky events, and the
ClientWidgetApiinmatrix-widget-apiwill filter them to only give access to the types that the current widget request permissions for.Note: We might want to ensure that the permission/capability text for
org.matrix.msc4407.receive.sticky_eventunlike other read capability give access to past history? (max 1h)Next: Do a playwright test with a simple widget displaying the state it got
Checklist
public/exportedsymbols have accurate TSDoc documentation.