Network requests still occurring after changing the conversation in talk
Open
Nobody has claimed this yet.
1. to develop
bug
feature: sync
performance 🚀
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
To Reproduce
Steps to reproduce the behavior:
- Go to conversation A that contains a shared text file, enable editing
- Observe that you see
syncandpushrequests - Change to conversation B
Expected behavior
You should not see any sync or push related requests anymore.
Actual behavior
Requests from the first conversation/document are still observed
Seen on 30.0.0 on c.nc.c
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Talk with a shared text file: observe sync and push requests in conversation A, then switch to conversation B. Trace the conversation-change handling and document synchronization entry points; done means requests from the first conversation or document stop after switching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100