max-mapper / max-mapper/workerstream
Debugger interferes with message order
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 92
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In a similar setup with iframes instead of workers, I've noticed that using the debugger can jumble up the ordering of incoming messages emitted with postMessage. Not sure if the worker has the same problem.
You can close this issue once you've read it.
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
The issue names no files, tests, or entry points. Start by determining whether the reported debugger-related message reordering also occurs with HTML5 workers and postMessage; done would require a confirmed worker reproduction or a clear conclusion that the issue should be closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100