Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 12 commits
- 9 files changed
- 4 contributors
Commits on Jan 10, 2025
Commits on Apr 20, 2025
Commits on Jan 7, 2026
-
-
fix: #294 Closing tag is missing but valid HTML is still not parseable
With this change, the valid HTML > `<body><main class=h-entry><p>hello</main></body>` is parsed correctly. Furthermore, p element close tags may be omitted according to the [spec](https://html.spec.whatwg.org/multipage/grouping-content.html#the-p-element) if: > there is no more content in the parent element and the parent element is an HTML element that is not an a, audio, del, ins, map, noscript, or video element, or an autonomous custom element. With this change, all these cases are handled correctly With the exception that there is no exclusion of autonomous custom elements so that p elements will be closed incorrectly when they are contained in such. However, it is not immediately obvious that node-html-parser supports autonomous custom elements, so this omission may not be significant.
-
Within valid.js, the test 'hillcrestpartyrentals.html should return Object with valid: false. not closing <p> tag on line 476' was implemented incorrectly. In fact the HTML is valid. All the p elements without close tags are contained in td elements and, therefore, the closing tag is not required. The return should be true.
-
Test for #227 was broken by previous commit. This fixes it. All tests are now passing.
-
Merge pull request #288 from olets/285-document-wrapper-node
docs: `parse()` always adds a wrapper node [#285]
-
Merge pull request #292 from fiddleplum/o-291
#291 Made id also update attributes.
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.0.1...v7.0.2