Render against a document other than window.document
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36.1k
- Forks
- 1.1k
- Avg merge
- 9h 18m
- Merged PRs (30d)
- 195
Description
Moved from ryansolid/dom-expressions#253 / the layering discussion on solid#1740.
template() / createElement always hit global document. Scoped custom element registries and shadow-root-backed documents need the mount root’s document-like object instead.
#1740 put a document field on the reactive owner. That was rejected because it puts DOM-specific state into the owner. The gap is still real; the enhancement is a renderer-owned document (or equivalent) that does not leak into rxcore.
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
Start by tracing the renderer entry points used by template() and createElement, then review the linked layering discussion and the rejected reactive-owner approach. Define how the mount root supplies a document-like object for scoped registries and shadow-root-backed documents; done means rendering no longer relies on the global document without leaking DOM state into rxcore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100