-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Block Bindings: Preserve nested inner blocks when binding rich text #12113
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
Open
cbravobernal
wants to merge
10
commits into
WordPress:trunk
Choose a base branch
from
cbravobernal:try/block-bindings-preserve-inner-blocks
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+598
−12
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
5ae3f96
Block Bindings: Preserve nested inner blocks when binding rich text.
cbravobernal d3ba090
Block Bindings: Enable native List Item content binding and expand te…
cbravobernal 8674661
Tests: Reference Trac ticket on List Item binding tests.
cbravobernal 31ba838
Docs: Tidy WP_Block inner-block-offset docblocks.
cbravobernal c449a16
Block Bindings: Harden inner-block offset handling from review.
cbravobernal 7f102c3
Docs: Clarify the set_inner_html TODO in WP_Block::replace_html.
cbravobernal 9cf3cf6
Block Bindings: Address self-review of List Item binding support.
cbravobernal f98e0b8
Tests: Use assertEqualHTML for block bindings rendered markup.
cbravobernal edac6d1
Block Bindings: Keep inner-block offsets across no-op replacements.
cbravobernal 48a00b5
Tests: Cover binding when an inner block precedes the rich text.
cbravobernal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this always hold? Specifically:
Another way we might do this is to find all the text nodes from the block start to the first inner block and that becomes the replacement range. We could use a Tag Processor on that range to ensure that everything is, in fact, text.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For
core/list-item, yes. The block renders its innerContent in order: own rich-text first, then the inner-block placeholders. The offsets are recorded in that same render loop, so the first offset is probably where the rich text ends.For an arbitrary block or manual markup, it's not guaranteed. I'll add a test.
On the Tag Processor idea
On finding the range by walking text nodes: the range isn't always text. It can contain raw block markup that should be replaced, right next to a real inner block that shouldn't, and they look identical once rendered. The offset is the only thing that knows which
<ul>came from an actual inner block.Still, I would need to add a test to be really sure about it.