riot-web
https://github.com/vector-im/riot-web
JavaScript
A glossy Matrix collaboration client for the web.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
JavaScript not yet supported160 Subscribers
Add a CodeTriage badge to riot-web
Help out
- Issues
- Distinguish room state and timeline events when dealing with widgets
- Flaky playwright test: `read-receipts/redactions-main-timeline.spec.ts: Sending and redacting a message after marking the room as read makes it read`
- Flaky playwright test: `read-receipts/new-messages-in-threads.spec.ts: A room where all threaded messages are read is still read after restart`
- Flaky playwright test: `read-receipts/redactions-in-threads.spec.ts: Reading a thread root when its only message has been redacted leaves the room read`
- Flaky playwright test: `read-receipts/editing-messages-in-threads.spec.ts: A room where all threaded edits are read is still read after restart`
- Flaky playwright test: `read-receipts/new-messages-in-threads.spec.ts: Reading the last threaded message makes the room read`
- Flaky playwright test: `read-receipts/new-messages-in-threads.spec.ts: Sending a new different-thread message after marking as read makes it unread`
- Flaky playwright test: `read-receipts/new-messages-in-threads.spec.ts: Reading the main timeline does not mark a thread message as read`
- Flaky playwright test: `read-receipts/editing-messages-in-threads.spec.ts: A room with an edited threaded message is still read after restart`
- Flaky playwright test: `read-receipts/redactions-main-timeline.spec.ts: Reacting to a redacted message leaves the room read`
- Docs
- JavaScript not yet supported