Skip to content

docs(js): describe parser-backed extraction #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jt55401 merged 1 commit into from
Aug 28, 2026
Merged

docs(js): describe parser-backed extraction #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions javascript/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -284,10 +284,10 @@ function finalizeCanonicalParts(parts) {
* 5. Decodes HTML entities.
* 6. Applies the full text normalization pipeline (`normalizeText`).
*
* This implementation is regex-based and is sufficient for signed content
* as typically produced by CMS platforms (blog posts, articles, news
* stories). For pathological or adversarial input, a real DOM parser
* should be used instead; the library API is compatible.
* The fragment is parsed with parse5, then walked as a DOM. A portable-profile
* validation pass rejects parser recovery and unsupported input before the
* parsed tree is traversed, so the same input produces the same result across
* bindings.
*
* @param {string} html - HTML fragment to canonicalize
* @param {object} [options] - Options passed through to normalizeText
Expand Down
Loading