Avoiding nesting like pre > p or p > h2 that works but aren't valid in html
Open
Nobody has claimed this yet.
ContentEditableTrue
execCommand
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
With Chrome you can end up with such nesting, not only they are not valid in HTML, but you can't un-nest the blocks.
Firefox maintains a low depth of blocks, I believe it's a good approach
There are no specs, but are what are the thoughts on this?
Contributor guide
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
No repository files or tests are named. Start by reviewing the linked Chromium issue and comparing the described nesting behavior with Firefox, then clarify the desired handling of invalid HTML nesting and document the agreed outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100