-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Dragging a wide block can cause blocks to overlap other blocks #4
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
Comments
Still not showing up on Chrome |
I've reproduced this in Chrome: http://i.imgur.com/zJH2R.png |
+1 for fixing this issue. ... running into major problems with large blocks . ! ... I've noticed that the issue is more pronounced in handheld devices with touch (iPad). This occurs in almost all browsers (Chrome and FF tested). There's also another issue where moving around a large block will cause other blocks to not automatically adjust to the topmost available space and they stay a row or two below the space where they would otherwise fit, the blocks do not adjust position to the space directly above even when there is ample space above these small blocks. This issue is probably related to the large block overlap issue. |
This solves the overlapping-blocks seen in the screencast provided by @daniel-nelson. I've captured another one trying to reproduce the same movements with this commit applied: http://www.screenr.com/g7J8
+1 We also have this problem! plase fix this issue... |
+1 |
Let us know if there is a way to fix it or if we have to start quitting using grister. |
..and everything is working again! |
Btw. we are seeing the same problem... |
thanks @bastianonm 👍 |
@vieron any chance @bastianonm's PR could be merged in? |
Thank you, @bastianonm, this was causing me headaches! I think this change should definitely be merged. |
Merged here 31fd8d6 |
This issue hasn't been solved perfectly yet. I can still get blocks overlapping even if none of blocks is dragged. They just overlap after the creation with API |
Easiest to convey this with a video: http://screencast.com/t/05wwm3l9Yfp
The text was updated successfully, but these errors were encountered: