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

Dragging handle back into its anchor makes its opposite handle move around randomly #2451

Open
Keavon opened this issue Mar 17, 2025 · 4 comments
Labels
Good First Issue Good for newcomers

Comments

@Keavon
Copy link
Member

Keavon commented Mar 17, 2025

We no longer can snap a handle to its anchor point, thereby hiding it (giving it a zero length status where it's treated as gone). When doing this, the other handle shouldn't be affected from its original position.

See the video in my comment below for what this issue is now about.

@Keavon Keavon added the Good First Issue Good for newcomers label Mar 17, 2025
@github-project-automation github-project-automation bot moved this to Short-Term in Task Board Mar 17, 2025
@0SlowPoke0
Copy link
Contributor

@Keavon this was fixed right?

@Keavon
Copy link
Member Author

Keavon commented Mar 17, 2025

Hmm, yeah, seems to be and that does align with my memory. I moved this over from the ✅ issue in #code-todo-list (which I deleted when transferring this over to here to avoid duplication), prompted by @mTvare6 referencing that #code-todo-list task link in a TODO comment in the code of #2450. So I tested it and saw it was broken in dev. So I replaced it with this issue and updated the URL of the TODO comment to this issue. But now it's not present as far as I can tell.

However, when testing just now, I did find this similar bug. Let's make this issue now dedicated to fixing this bug:

capture_53_.mp4

@mTvare6
Copy link
Contributor

mTvare6 commented Mar 18, 2025

Hmm, yeah, seems to be and that does align with my memory. I moved this over from the ✅ issue in #code-todo-list (which I deleted when transferring this over to here to avoid duplication), prompted by @mTvare6 referencing that #code-todo-list task link in a TODO comment in the code of #2450. So I tested it and saw it was broken in dev. So I replaced it with this issue and updated the URL of the TODO comment to this issue. But now it's not present as far as I can tell.

However, when testing just now, I did find this similar bug. Let's make this issue now dedicated to fixing this bug:

capture_53_.mp4

The code already did mention that issue once, I just moved it over into common handler, sorry for not checking if it were resolved.

@Keavon
Copy link
Member Author

Keavon commented Mar 18, 2025

Oh I missed that you were just moving that code, my bad. Mystery solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue Good for newcomers
Projects
Status: Short-Term
Development

No branches or pull requests

3 participants