ProjectEvergreen / ProjectEvergreen/wcc
expand (no-op) support of DOM shim for DOM traversal methods
Open
feature
question
- Dominant language
- JavaScript
- Stars
- 126
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Type of Change
- New Feature Request
Summary
Tracking a number of items that I think the DOM shim should be able to support, though I'm not sure how feasible / realistic any of them are, so will need to do some discovery of what makes sense to fall "in bounds" for SSR, short of just becoming a headless browser.
Details
Not sure how many of these can / should be supported, but some of them at least, if not at least for no-ops
- parentNodes
-
querySelector/querySelectorAll -
getElementBy[Id|ClassName|TagName|...] - Node <> Element <> HTMLElement (ensure proper inheritance hierarchy)
Questions
- Is
appendNodeimplemented correctly? - Use ASTs in DOM shim (?)
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.
Assessment
This issue has not been assessed yet.