Simple Todos Hyperscript demo is broken
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start at the Simple Todos Hyperscript demo at https://www.solidjs.com/examples/simpletodoshyperscript and reproduce the failure by adding one item, then another. Inspect the browser console error and compare behavior in Chrome or Firefox. Done means multiple todo items can be added successfully without the reported DOMNode._children error.
Written by the indexing model from the issue text.
Description
Describe the bug
This demo does not work: https://www.solidjs.com/examples/simpletodoshyperscript
After adding the first todo item, all other items do not get added. There is an error in browser console
sdk.js:1 Uncaught Error: DOMNode._children is expected to not be null.
at Tn.insertChild (sdk.js:1:257639)
at Pn.childNodeInserted (sdk.js:1:268559)
at Ln.childNodeInserted (sdk.js:1:273663)
at g.dispatch (protocol_client.js:1:7253)
at j.dispatch (protocol_client.js:1:8244)
at d.onMessage (protocol_client.js:1:4221)
at sdk.js:1:341593
Your Example Website or App
https://www.solidjs.com/examples/simpletodoshyperscript
Steps to Reproduce the Bug or Issue
- Go to https://www.solidjs.com/examples/simpletodoshyperscript
- Try adding new todo items
- After adding the first one, they stop working
Expected behavior
The demo should work
Screenshots or Videos
See the attached video. The recording uses Chrome v134, but I see the same in Firefox 136 too (both are latest stable versions)
https://github.com/user-attachments/assets/c16e6f4a-fb68-4a95-b248-0177e92487a2
Platform
- OS: n/a
- Browser: Chrome v134, Firefox 136
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 178
- Avg merge
- 10h 38m
- Merged PRs (30d)
- 1
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.
More from solidjs/solid-site
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
solidjs/solid-site#586 ·
-
Newsletter “registration could not be completed” due to newsletter.solidjs.com ERR_NAME_NOT_RESOLVED Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
solidjs/solid-site#588 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
solidjs/solid-site#584 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
solidjs/solid-site#583 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
solidjs/solid-site#577 ·
All issues in solidjs/solid-site
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100