Bernhard Reiter 5a32396d8f HTML API: Accumulate shift for internal parsing pointer. ... A bug was discovered where where the parser wasn't returning to the start of the affected tag after making some updates. In few words, the Tag Processor has not been treating its own internal pointer `bytes_already_parsed` the same way it treats its bookmarks. That is, when updates are applied to the input document and then `get_updated_html()` is called, the internal pointer transfers to the newly-updated content as if no updates had been applied since the previous call to `get_updated_html()`. In this patch we're creating a new "shift accumulator" to account for all of the updates that accrue before calling `get_updated_html()`. This accumulated shift will be applied when swapping the input document with the output buffer, which should result in the pointer pointing to the same logical spot in the document it did before the udpate. In effect this patch adds a single workaround for treating the internal pointer like a bookmark, plus a temporary pointer which points to the beginning of the current tag when calling `get_updated_html()`. This will preserve the assumption that updating a document doesn't move that pointer, or shift which tag is currently matched. Props dmsnell, zieladam. Fixes #58179. Built from https://develop.svn.wordpress.org/trunk@55706 git-svn-id: http://core.svn.wordpress.org/trunk@55218 1a063a9b-81f0-0310-95a4-ce76da25c4cd		2023-05-03 11:31:18 +00:00
..
class-wp-html-attribute-token.php
class-wp-html-span.php
class-wp-html-tag-processor.php	HTML API: Accumulate shift for internal parsing pointer.	2023-05-03 11:31:18 +00:00
class-wp-html-text-replacement.php