-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Flyout doesn't match intended design #340
Comments
Look at line 1145 of Through testing, |
Still new to this so correct me if I'm wrong. Lines 1156 - 1174 in
Specifically these lines:
These lines look like they control how the block is placed in the flyout. If we used this:
It should make the blocks center properly (I think). Testing now. EDIT: I was wrong. That controls the size of the rect that the block is in - not where it's placed in the flyout. |
Hey there! There's a big merge coming in soon that may fix some problems: google/blockly#291 makes the horizontal toolbox much more robust and deals with RTL properly, among other things. I'll be merging google/develop in again soon (hopefully today or tomorrow), so line numbers will change significantly soon. I think the problem with aligning by baseline will still be present post-merge. The top margin may be correct. |
Thanks for looking at this, @Tymewalk! Here are the steps I follow to link to a line:
It would be nice if GitHub did this automatically when you start typing something like core/flyout.js:1156, just like it helps you with PRs and issues when you type # or names when you type @... |
Merge PR is #350 The baseline problem is definitely still present. |
Tracking in #21 |
If you load the default toolbox, eg with tests/horizontal_playground.html, you see a flyout as below:
This has the following issues:
The intended design is shown in this screenshot from the blog post:
The text was updated successfully, but these errors were encountered: