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

Chrome Android: Cannot invoke workspace context with long press #2188

Open
AnmAtAnm opened this issue Dec 19, 2018 · 2 comments
Open

Chrome Android: Cannot invoke workspace context with long press #2188

AnmAtAnm opened this issue Dec 19, 2018 · 2 comments
Labels
component: browser component: touch help wanted External contributions actively solicited issue: bug Describes why the code or behaviour is wrong low priority

Comments

@AnmAtAnm
Copy link
Contributor

AnmAtAnm commented Dec 19, 2018

Problem statement

Long press on empty workspace area does not invoke the Blockly context menu.

Expected Behavior

A long press on empty workspace should pop open the context menu if options like "Delete blocks".

Actual Behavior

The long press selects some text. It may be label text in a block in the toolbox, as shown:
screenshot_20181219-104813

Or it may be text adjacent to the workspace, particularly if the toolbox flyout is not open.

Long press on a block will open the expected context menu.

Steps to Reproduce

  1. On an Android device with a recent version of Chrome, open any page with blockly.
  2. Optionally add a block to the workspace from the toolbox or by loading a workspace.
  3. On a blank space on the workspace, long press.
  4. Note that the context menu did not come up, and now there is a text word selected, possibly on a block field_label.

Operating System and Browser

  • Android Pixel 2XL:
    • OS: Android 9
    • Browser: Chrome
    • Version 71.0.3578.99

Additional Information

Given #2187 is also related to Android Chrome, is also touch related, and is also seen in master.

@surajguduru
Copy link

Hey @AnmAtAnm I would like work on this issue. Can you assign it to me ?

@BeksOmega
Copy link
Collaborator

@surajguduru Do you have an Android device to test with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: browser component: touch help wanted External contributions actively solicited issue: bug Describes why the code or behaviour is wrong low priority
Projects
None yet
Development

No branches or pull requests

3 participants