Changes tab, ObservableMap open error.
Open
Nobody has claimed this yet.
can't reproduce
- Dominant language
- JavaScript
- Stars
- 502
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I use Changes tab and click to ObservableMap@5{...} +1 -1,
not working.
chrome console error
backend.js:4189 Uncaught DOMException: Failed to execute 'postMessage' on 'Window': [object Object] could not be cloned.
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
Reproduce the failure by opening an ObservableMap entry from the Changes tab, then inspect backend.js around line 4189 and the postMessage call reported by Chrome. Done means the ObservableMap entry opens without the DOMException about cloning [object Object].
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100