Skip to content

Clarify which input a block is being moved into #9497

New issue
New issue
Closed
Feature
Closed
Clarify which input a block is being moved into#9497
Feature
Assignees
mikeharv

Description

@gonfunko
gonfunko
opened on Dec 2, 2025

Currently, when a block is in constrained move mode, potential destinations are identified by reading out the proposed-parent block's label. In cases where the parent block has multiple (value or statement) inputs however, the input in question is not identified, which makes it challenging to place blocks. This should be improved, perhaps by using the field row label, index of the input or another method.

Activity

  1. gonfunko
    added this to Blocklyon Dec 2, 2025
  2. gonfunko
    added the
    Feature
    issue type on Dec 2, 2025
  3. github-project-automation
    moved this to Todo in Blocklyon Dec 2, 2025

  4. BenHenning commented on Dec 4, 2025

    @BenHenning
    BenHenning
    on Dec 4, 2025
    Contributor

    From @microbit-robert:

    This is specifically a move mode issue, where it's not clear at the moment which branch of an if statement you are moving a block into. I can provide a diff of what I've done here shortly.

    These are the changes we've made for move mode for user testing in isolation which includes handling the specific branch for if / else blocks https://github.com/RaspberryPiFoundation/blockly/compare/add-screen-reader-support-experimental...microbit-matt-hillsdon:blockly:move-mode-changes

    This actually works better for MakeCode's if blocks than the Blockly test page if blocks. As the MakeCode blocks don't have the "do" text preceding the statement inputs, we use the text on the previous row. In the Blockly test page case, all 'else if' statements are labelled as "do", which can still be confusing.

  5. joreneng commented on Dec 12, 2025

    @joreneng
    joreneng
    on Dec 12, 2025

    Adding a note that this was also a pain point with all of the user testers in this testing round.

  6. jversloot commented on Dec 15, 2025

    @jversloot
    jversloot
    on Dec 15, 2025

    This was also an issue in our user tests with users moving their focus into a block and onto number inputs, and only being read out the value of the number, and not a title of what field they are focused on. Not sure if this is the same issue as when in move mode so I wanted to bring it up but can log it separately if it is different.

  7. maribethb commented on Apr 8, 2026

    @maribethb
    maribethb
    on Apr 8, 2026
    Contributor

    Also relevant to #9686

  8. mikeharv
    self-assigned this
    on Apr 20, 2026
  9. mikeharv
    closed this as completedon Apr 20, 2026
  10. github-project-automation
    moved this from Todo to Done in Blocklyon Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Feature

Projects

  • Blockly
    Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions