Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML API: Add spawn fragment parser method #22

Conversation

sirreal
Copy link
Collaborator

@sirreal sirreal commented Sep 12, 2024

Implements https://html.spec.whatwg.org/multipage/parsing.html#html-fragment-parsing-algorithm

Trac ticket:

 OK, but incomplete, skipped, or risky tests!
-Tests: 1500, Assertions: 1079, Skipped: 421.
+Tests: 1686, Assertions: 1222, Skipped: 464.

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

private function spawn_fragment_parser( string $html ): ?self {
if ( $this->get_token_type() !== '#tag' ) {
return null;
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably bail on closers too.

Maybe bail on virtual tokens?

@sirreal sirreal changed the title Html api/spawn fragment parser HTML API: Add spawn fragment parser method Sep 12, 2024
When fragments were used instead of full processors, some fake tree
structure had to be prepended to the output.

This is no longer necessary and breaks the fragment cases.
This condition:

> Reprocess the token according to the rules given in the section
> corresponding to the current insertion mode in HTML content.

Was resulting in an infinite loop in fragment cases. In full documents,
after popping nodes the context is always moved so that foreign content
parsing is not used. This is not guaranteed in a fragment and could
cause an infinite loop.
@sirreal
Copy link
Collaborator Author

sirreal commented Sep 13, 2024

Proposed on its own in WordPress#7348

@sirreal
Copy link
Collaborator Author

sirreal commented Nov 6, 2024

Closing in favor of WordPress#7348

@sirreal sirreal closed this Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant