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

chore: fix mutator blocks jumping #6559

Merged
merged 2 commits into from
Oct 18, 2022

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 #6541

Proposed Changes

Reverts changes made in #6301 that caused jumping.

Reason for Changes

Bugs are bad.

Test Coverage

Manually tested the repro steps from #6541

Documentation

N/A

Additional Information

Thank you to Maribeth for the bisect + cherrypick idea!

Also for now I've just reverted the bug-causing changes. But I'm also going to file a bug for actually refactoring this system to be more testable + less stateful + not use private properties on svg elements.

@BeksOmega BeksOmega requested a review from a team as a code owner October 18, 2022 16:54
@BeksOmega BeksOmega requested a review from gonfunko October 18, 2022 16:54
@github-actions github-actions bot added the PR: chore General chores (dependencies, typos, etc) label Oct 18, 2022
@BeksOmega BeksOmega requested review from maribethb and removed request for gonfunko October 18, 2022 18:17
@BeksOmega BeksOmega assigned maribethb and unassigned gonfunko Oct 18, 2022
Copy link
Contributor

@maribethb maribethb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spent a long time trying to understand the original change + this.

It looks like before the original change the transform attribute was set to skew + translate, and after that change it's only set to skew. I wonder if that's the whole problem?

Or part of the problem is block_svg is still using the skew_ and translate_ properties, so if we just don't set them here, things go weird?

Either way this change LGTM and also filing a bug to fix this up is good.

@BeksOmega BeksOmega merged commit 04dffbc into google:develop Oct 18, 2022
cpcallen pushed a commit to cpcallen/blockly that referenced this pull request Oct 19, 2022
* chore: fix mutator blocks jumping

* chore: format
This was referenced Oct 19, 2022
@BeksOmega BeksOmega deleted the fix/mutator-blocks-jumping branch May 14, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: chore General chores (dependencies, typos, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mutator stacks are broken in current master
3 participants