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

npm: new blocks instances appear below menuFlyout while dragging #3032

Closed
microspace opened this issue Sep 17, 2019 · 3 comments
Closed

npm: new blocks instances appear below menuFlyout while dragging #3032

microspace opened this issue Sep 17, 2019 · 3 comments
Assignees
Labels
component: demos issue: bug Describes why the code or behaviour is wrong

Comments

@microspace
Copy link

microspace commented Sep 17, 2019

Blocks always go under menuflyout when I drag clock to create new block instance.
Issue appears when I use npm package of blockly

Steps to reproduce the behavior:

  1. Go to https://github.com/google/blockly-samples/tree/master/blockly-webpack
  2. clone, npm install, npm run start
  3. Drag any of block from toolbox.
  4. See error: block appears below menuFlyout

Снимок

Desktop:

  • OS: Windows 10
  • Chrome browser
  • Version 76
@microspace microspace added issue: triage Issues awaiting triage by a Blockly team member issue: bug Describes why the code or behaviour is wrong labels Sep 17, 2019
@RoboErikG RoboErikG added component: demos and removed issue: triage Issues awaiting triage by a Blockly team member labels Sep 17, 2019
@samelhusseini
Copy link
Contributor

Fixed in develop. We are planning an npm release in a few weeks.

@microspace
Copy link
Author

@samelhusseini , thank you! Can I use the develop version for now, or it is not possible?

@RoboErikG
Copy link
Contributor

@microspace We don't publish our develop branch to npm, so if you would like to use it you'll have to clone it from the GitHub repo.

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

No branches or pull requests

3 participants