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

Code Demo: Edge stops responding to touch #1942

Closed
AnmAtAnm opened this issue Jun 26, 2018 · 2 comments
Closed

Code Demo: Edge stops responding to touch #1942

AnmAtAnm opened this issue Jun 26, 2018 · 2 comments
Labels
component: browser component: demos issue: bug Describes why the code or behaviour is wrong

Comments

@AnmAtAnm
Copy link
Contributor

AnmAtAnm commented Jun 26, 2018

Problem statement

Expected Behavior

Blockly should never stop reacting to touch input.

Actual Behavior

The Blockly workspace in the code demo stops reacting to touch events after a very specific sequence involving select the XML tab.

Steps to Reproduce

  1. Open Edge on a touch device such as a Surface.
  2. Open the Blockly Code Demo.
  3. Add some blocks to the workspace. Observe how dragging and block connections work just fine.
  4. Tap on the XML tab and then return via the Blocks tab.
  5. Attempt to pan the workspace. Observe how the workspace stops responding to touch event such as the pan gesture after about one redraw. The user cannot select a block, a field, and toolbox interaction usually fails.

The same behavior works fine in Chrome and IE on the same device.

This was observed on both the previous release / master branch and the release candidate branch.

Stack Traces

The sequence did not produce any error in the console.

Operating System and Browser

  • Windows Edge
@AnmAtAnm
Copy link
Contributor Author

The bug is specific to the XML tab in the demo. The workspace works fine after return from a generator tab.

The show and hide on the playground does not trigger the problem.

@alschmiedt
Copy link
Contributor

Closing because can't repro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: browser component: demos issue: bug Describes why the code or behaviour is wrong
Projects
None yet
Development

No branches or pull requests

3 participants