max-mapper / max-mapper/monocles
periodic stream refreshing is disruptive
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
When the _changes event fires the whole stream redraws itself, which can be disruptive. It especially problematic if the user is in the process of writing a comment or browsing a comment thread.
I suggest a notification at the top of the stream that is updated on _changes. The user should be able to click on the notification to refresh the stream.
Contributor guide
No contributing guide indexed for this repository
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
Trace the stream rendering code and the _changes event handling mentioned in the issue. Confirm where the full redraw is triggered, then determine how a top-of-stream notification could defer refreshing until clicked. Done means updates no longer disrupt comment writing or thread browsing, while the notification still refreshes the stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100