Open t-hamano opened 4 days ago
Thanks for catching the bug and creating the issue. It seems the new behavior to "compute insertion point" on the fly should only apply to specific conditions, not all the conditions of when a block is visible or not.
So it's like we need two different kind of selectors:
I'll explore something.
We should have e2e tests about the "manage block visibility" thing
What problem does this address?
I found two issues in the trunk:
I used
git bisect
and it looks like this issue occurred in #65490.https://github.com/user-attachments/assets/e9b761f6-79a2-4ab9-bde3-86b031d5e755
cc @youknowriad @andrewserong @jorgefilipecosta