Skip to content
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

fix: insertion markers firing move events #7005

Merged
merged 1 commit into from
Apr 21, 2023

Conversation

BeksOmega
Copy link
Collaborator

The basics

  • I branched from develop
  • My pull request is against develop
  • My code follows the style guide
  • I ran npm run format and npm run lint

The details

Resolves

Fixes #7002

Proposed Changes

Reverts reordering hiding and connecting. It is more efficient to connect "on top" of another connection, because then we can avoid setting the block's parent element twice. But this only saves ~12ms from wrapping an if around the spaghetti blocks. So I think correctness is better in this case.

Test Coverage

Just manual testing.

Documentation

N/A

Additional Information

Broken by #6876

@BeksOmega BeksOmega requested a review from a team as a code owner April 21, 2023 19:23
@github-actions github-actions bot added the PR: fix Fixes a bug label Apr 21, 2023
@BeksOmega BeksOmega merged commit 35276e9 into google:develop Apr 21, 2023
BeksOmega added a commit that referenced this pull request Apr 26, 2023
@BeksOmega BeksOmega mentioned this pull request Apr 26, 2023
4 tasks
@BeksOmega BeksOmega deleted the fix/insertion-marker-events branch April 26, 2023 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: fix Fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Insertion markers get disconnected/reconnected before being deleted
2 participants