Tag Processor: Make $html field protected
#48681
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ockham
changed the title
$html field protected
adamziel
approved these changes
Mar 2, 2023
Contributor
Author
|
I'll cherry-pick this to the cc/ @priethor since I believe you're in charge of that release 😊 |
ockham
added a commit
that referenced
this pull request
Mar 2, 2023
In the 6.2 compat layer, make `WP_HTML_Tag_Processor`'s `$html` member `protected` to support subclassing. This is for parity with Code in WordPress 6.2, see WordPress/wordpress-develop#4112 and [r55402](https://core.trac.wordpress.org/changeset/55402).
Contributor
Author
|
Cherry-picked to |
This was referenced Mar 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
In the 6.2 compat layer, make
WP_HTML_Tag_Processor's$htmlmemberprotectedto support subclassing.Why?
For parity with Code in WP 6.2, authored by @dmsnell in WordPress/wordpress-develop#4112 and committed by @gziolo in r55402.