Add condition to not add any other disconnect event messages if there are already consecutive disconnect messages in the events and remove the reconnect event message if another disconnect happens immediately after, this way keeping the first disconnect and the latest reconnect.
Testing
Steps
Go to live data view
Either leave the browser tab unfocused for a long while or (easier) disconnect from Wi-Fi or internet a couple of times
See no consecutive disconnects/reconnects events.
Results
Checklist
[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
[ ] Documentation: Relevant documentation is added or updated.
[x] Testing: The steps/process to test this feature are clearly explained including testing for regressions.
[ ] Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
[ ] Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
[x] Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.
Summary
References #4685
Changes
Testing
Steps
Results
Checklist
README.mdfor the chosen target branch.CHANGELOG.md.CONTRIBUTING.md, there are no fixup commits left.