element-hq / element-hq/element-web

Converge on inconsistent network issue behaviours on Web and Android

Open
#18,894 0 comments 0 reactions 0 assignees View on GitHub
A-Timeline O-Occasional T-Enhancement X-Needs-Design X-Needs-Product
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Send message while the network is dropping out
-> Message is unsent and a warning appears
2. Re-establish network

On Web:
3. Get asked if messages should be deleted or re-sent:
![Screenshot from 2021-09-03 14-24-27](https://user-images.githubusercontent.com/51663/132012533-0223abef-21e7-4a6e-92a2-fa3018783d3b.png)

On Android:
3. No error appears against the message, it's not possible to delete the message and messages are automatically re-sent when network is re-established

### Development checklist
- [ ] Tagged as T-Enhancement and with correct A-* label
- [ ] Product team confirmed that this feature:
- [ ] …is on the roadmap or
- [ ] …could be added to the roadmap or developed by a community member
- [ ] Design team has signed off on the feature: design has been finalised by the Element design team and attached to this issue:
- [ ] Acceptance criteria (in scope) have been clearly defined:
- [ ] Product and Design have agreed on how this should be handled
- [ ] Acceptance criteria are updated based on ^
- [ ] Clearly defined issues are filed for relevant changes
- [ ] Behaviour is verified against iOS app
- [ ] Out of scope:
- [ ] Redesigning a new behaviour beyond convergence

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.