Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add affordance to indicate users can navigate within blocks #105

Open
cpcallen opened this issue Nov 8, 2024 · 4 comments
Open

Add affordance to indicate users can navigate within blocks #105

cpcallen opened this issue Nov 8, 2024 · 4 comments
Assignees

Comments

@cpcallen
Copy link
Contributor

cpcallen commented Nov 8, 2024

During user testing, it was noted in many cases that the user did not realise they could use the right arrow key to navigate to the fields and inputs of the block the cursor was on.

It was suggested that we should provide some kind of affordance to make it clear that they can navigate within the block using the right arrow key. Ideas mooted included:

  • Have the enter key move to the first field of the block, or open a menu of suitable actions (e.g. "replace this block", "edit block settings").
  • Display a tooltip or other pop-up hint ("press right to access contents ->"?) to indicate it is possible to access the contents of the block.
    • Display of such hints could be disabled after the first time they are successfully applied.

See also #104.

@cpcallen cpcallen self-assigned this Nov 8, 2024
@cpcallen
Copy link
Contributor Author

cpcallen commented Nov 8, 2024

Based on post-testing conversations this is nominally a fairly high-piority item (I've categorised as P1), but as I'm not sure exactly what form this affordance should take I'm not sure how to proceed.

@cpcallen
Copy link
Contributor Author

It is planned to resolve this via an "edit contents" item in the context menu (see #132), which will be displayed when the user presses enter while focus is on a block (see #130).

@rachel-fenichel
Copy link
Contributor

@cpcallen I think this belongs in the micro:bit test milestone.

@kmcnaught
Copy link

Just to note that this could be resolved via an "edit contents" item in the context menu, or via a toast/notification, depending on the details of the flow (as per Matt's different options he's been experimenting with)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

3 participants