![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#59167 closed defect (bug) (fixed)
HTML API: Stop proceeding HTML when encountering unsupported markup.
| Reported by: | dmsnell | Owned by: | Bernhard Reiter |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.4 |
| Component: | HTML API | Version: | 6.4 |
| Severity: | normal | Keywords: | has-patch has-unit-tests commit |
| Cc: | Focuses: |
Description
It was a design goal of the HTML Processor to abort processing its input document when encountering unsupported markup. Unfortunately there was no test for this and so-far, the HTML Processor has paused, but continued processing in these situations.
In this patch a new test ensures that the HTML Processor stops and refuses to move forward after encountering any unsupported markup. It also ensures that it doesn't report any current tag names since unsupported markup could imply that the read tag name is different than the parsed tag name.
Change History (4)
This ticket was mentioned in PR #5048 on WordPress/wordpress-develop by @dmsnell.
3 years ago
#1
- Keywords has-unit-tests added
@Bernhard Reiter commented on PR #5048:
3 years ago
#4
Committed to Core in https://core.trac.wordpress.org/changeset/56493.
Note:
See TracTickets
for help on using tickets.
Trac ticket: #59167-trac
It was a design goal of the HTML Processor to abort processing its input document when encountering unsupported markup. Unfortunately there was no test for this and so-far, the HTML Processor has paused, but continued processing in these situations.
In this patch a new test ensures that the HTML Processor stops and refuses to move forward after encountering any unsupported markup. It also ensures that it doesn't report any current tag names since unsupported markup could imply that the read tag name is different than the parsed tag name.