| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-08-19 | break!: merge Tokenizer::new_with_emitter into Tokenizer::new | Martin Fischer | |
| The Tokenizer does not perform any state switching, since proper state switching requires a feedback loop between tokenization and DOM tree building. Using the Tokenizer directly therefore is a bit of a pitfall, since you might not expect it to e.g. tokenize `<script><b>` as: StartTag(StartTag { name: "script", .. }) StartTag(StartTag { name: "b", .. }) Since we don't want to make walking into pitfalls particularly easy, this commit changes the Tokenizer::new method so that you have to specify the Emitter. Since this makes new_with_emitter redundant it is removed. | |||
| 2023-08-19 | break!: remove StartTag::next_state | Martin Fischer | |
| You shouldn't manually have to match tokens yielded by the tokenizer iterator just to correctly handle state transitions. A better NaiveParser API will be introduced. | |||
| 2021-12-05 | rename to html5tokenizer, bump versionv0.4.0 | Martin Fischer | |
| 2021-12-05 | introduce StartTag::next_state | Martin Fischer | |
| Closes #11. | |||
| 2021-12-03 | Fix typo and add example (#9) | Martin Fischer | |
 |
index : html5tokenizer | |
| Fork of html5gum with code span support |
| aboutsummaryrefslogtreecommitdiff |