Unify named character reference tokenizer of xml5ever and html5ever
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 288
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
https://github.com/servo/html5ever/commit/46a9b0a6b1d30682e2b6decb60b45f8432b34cbf#diff-4969d7c75c41dbd134d41920b1ae213f6f7169044659add391e38f32ab156cde pretty much copied the character reference tokenizer from html5ever to xml5ever. We could put it in a shared crate (like markup5ever) instead.
This would be useful for https://github.com/servo/html5ever/pull/645.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by comparing the character-reference tokenizer in the linked html5ever commit with its xml5ever counterpart, then inspect the markup5ever crate as a possible shared location. Done means both parsers use one shared tokenizer implementation and the change supports html5ever pull request 645.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100