-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
December 2018 release #2174
December 2018 release #2174
Conversation
Fixes #2096 We were creating a text node to wrap any block connected to next when we should have just been attaching the generated dom.
Update version number
…_checkbox Select generator test suites by checkbox
…n_browser Run generator tests on Travis
Bad commit during debugging.
#172, Fixed [Edge, IE] Zoom control mouseover is not clipped
Fixes #1653 Makes the bounds checker created in inject correctly set the event group before moving blocks in bounds. When a workspace can't scroll the inject method sets up an event listener to bump blocks back into the visible bounds when dropped off the edge. The event group wasn't being used, though, causing the move to be a separate undo step. When undone, this would get you stuck in a loop where the workspace would keep pulling it back into the visible range.
Reconnects child blocks when an undo is done on an else block
Groups events fired during field input change
Disable insertion markers for the December 2018 release
Update dependencies
Rebuild uncompressed and language files
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
Fixes #1958 This will drop the input when it's in the empty string state. This causes the block to remove the input and re-add it when the text is reverted, but prevents the breakage. A followup fix should leave the input alone instead of removing it, but this works for now.
Avoid crashing when a procedure input has an empty string
Issues closed
Pull requests