HTML API: Reset parser state after seeking to bookmark.
When parser states were introduced, nothing in the `seek()` method reset the parser state. This is problematic because it could leave the parser in the wrong state. In this patch the parser state is reset so that it's properly adjusted on the successive call to `next_token()`. Developed in https://github.com/WordPress/wordpress-develop/pull/6021 Discussed in https://core.trac.wordpress.org/ticket/60428 Follow-up to [57211] Props dmsnell, kevin940726 Fixes #60428 Built from https://develop.svn.wordpress.org/trunk@57527 git-svn-id: http://core.svn.wordpress.org/trunk@57028 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
parent
742e8aae9c
commit
22b4a0870d
|
@ -2335,6 +2335,7 @@ class WP_HTML_Tag_Processor {
|
|||
|
||||
// Point this tag processor before the sought tag opener and consume it.
|
||||
$this->bytes_already_parsed = $this->bookmarks[ $bookmark_name ]->start;
|
||||
$this->parser_state = self::STATE_READY;
|
||||
return $this->next_token();
|
||||
}
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@
|
|||
*
|
||||
* @global string $wp_version
|
||||
*/
|
||||
$wp_version = '6.5-alpha-57526';
|
||||
$wp_version = '6.5-alpha-57527';
|
||||
|
||||
/**
|
||||
* Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.
|
||||
|
|
Loading…
Reference in New Issue