Skip to content

Moving blocks to closest connection is confusing when moving from below-blocks workspace position #10024

@mikeharv

Description

@mikeharv

Check for duplicates

  • I have searched for similar issues before opening a new one.

Description

When a block is moved via constrained move mode below the other blocks, and then moved back up, it will move to the closest connection, which is not necessarily the last connection:

Screen.Recording.2026-06-17.at.13.10.40.mov

As reported:

Once I'm at the bottom workspace position, I then go back up one position, but to a blind user, I've gone 'up' 3 positions and it's not clear why. A blind user doesn't know that moving to the bottom workspace position means moving to the bottom left of the last block.

Reproduction steps

  1. Add a controls_for and math_number block to the workspace.
  2. Use keyboard move mode (constrained) to move the number block below the loop.
  3. Move the number block up or left once.

Instead of moving to the 'by' input, the block is moved to the 'from' input. This might make sense to sighted users but not un-sighted users.

Priority

No response

Stack trace

Screenshots

No response

Browsers

No response

Metadata

Metadata

Assignees

Labels

issue: bugDescribes why the code or behaviour is wrongissue: triageIssues awaiting triage by a Blockly team member

Type

No type
No fields configured for issues without a type.

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions