XML5: incentive well-formed XHTML5: Output parsing errors on demand & provide best processing time for flawless code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 288
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
People are using xhtml because they expect to get a Yellow Screen of Death if code is wrong are interested in good code quality.
I followed the XML5 discussion and saw arguments to use its error corrections for broken RSS feeds and broken SVG inside html and such things, which would be useful for the lax html world.
Currently, there can't be broken xhtml files on the web because Firefox is strict.
Servo would make incentives to write bad xhtml, if the current behavior would be kept (to conceal faults).
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
The issue names no files, tests, or entry points; start by clarifying the desired XML5/XHTML5 error-reporting behavior and its processing-time requirement. Done criteria are not specified, so a maintainer decision is needed before implementation or validation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, xml
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100