HTML API: Stop counting noop seek operations against the max seek count.

[dmsnell]

Trac ticket: Core-62085

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props dmsnell, jonsurrell.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Trac Ticket Missing

This pull request is missing a link to a Trac ticket. For a contribution to be considered, there must be a corresponding ticket in Trac.

To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. More information about contributing to WordPress on GitHub can be found in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[sirreal]

🏓

[westonruter]

How will this impact (or not) WP_HTML_Processor::seek() since its actual bookmarks get prefixed with _?

wordpress-develop/src/wp-includes/html-api/class-wp-html-processor.php

Lines 5266 to 5275 in b071c28

	public function seek( $bookmark_name ): bool {
	// Flush any pending updates to the document before beginning.
	$this->get_updated_html();
	$actual_bookmark_name = "_{$bookmark_name}";
	$processor_started_at = $this->state->current_token
	? $this->bookmarks[ $this->state->current_token->bookmark_name ]->start
	: 0;
	$bookmark_starts_at = $this->bookmarks[ $actual_bookmark_name ]->start;
	$direction = $bookmark_starts_at > $processor_started_at ? 'forward' : 'backward';

[dmsnell]

it shouldn't because by the time it calls this parent-class method, it has supplied the underscore.

[westonruter]

OK, right. By the way, what is the reasoning behind prefixing bookmarks with underscores in HTML Processor? In WordPress/performance#1546 I'm making use of WP_HTML_Processor when available, but in the logic that injects additional markup into the head and body, it needs to obtain the start position of the bookmark. For the HTML Processor version it has to prepend the _ which seems strange, although granted this is an internal API:

• WP_HTML_Tag_Processor version
• WP_HTML_Processor version

[dmsnell]

the reason was to avoid any possible conflicts between bookmarks set by the HTML Processor itself, and the user-space code setting bookmarks. that is, any time someone calls WP_HTML_Processor::set_bookmark() it will be prefixed, but calls inside the processor to parent::set_bookmark() will be un-prefixed. it's a very basic namespacing mechanism.