Comments (1)
Hi, this is awesome news. default
tree adapter was an original tree format for parse5 and it was designed to fit better into W3C-proposed HTML5 parser algorithm. Later I've implemented htmlparser2
tree adapter, so parse5 can be plugged into existing solutions that uses htmlparser2 tree format. There is a little performance penalty, but it's pretty insignificant. For jsdom I suggest to keep htmlparser2 tree format because given performance benefits will not cost effort spent on the tree format change. However, htmlparser2
tree adapter just mimics HTML Node's interfaces provided by htmlparser2, many other details (like named entity representation in text nodes, tree-hierarchy) may obviously differ from htmlparser2 due to completely different parsing algorithm (but it will almost same as in modern browsers).
from parse5.
Related Issues (20)
- Expose createTextNode() on default tree adapter HOT 3
- Custom single closing tag can`t be parsed correctly HOT 1
- Rewriter trigger the "text" event even after the write callback is executed HOT 10
- Node types don't appear to be exported in an ergonomic way HOT 4
- Enable Keeping Attribute Name Casing HOT 9
- Adding config that allow for the use of self close tags HOT 1
- Failed to parse source map from file: Error: ENOENT: no such file or directory HOT 18
- parse5-html-rewriting-stream fails on file > 128kByte HOT 2
- Failed to parse source map ... HOT 3
- Package subpath './lib/parser/index.js' is not defined by "exports" HOT 2
- Incorrect handling of CDATA sections HOT 1
- browserify fails for parse5 HOT 1
- node_modules/parse5/dist/index.d.ts:1:15 - error TS1005: ',' expected. HOT 4
- Type definitions are not properly generated and typescript compile fails HOT 2
- Wrong HTML string when reading from a file with encoding utf8 with bom HOT 1
- Parsing messes up when given a utf-8 input with a BOM HOT 12
- The detachNode has not been called HOT 1
- Outlook VML statements become commented HOT 1
- Noframes tag not parsed according to specification when in body
- Migrate some or most methods of Tokenizer and Parser to `protected`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from parse5.