-
Notifications
You must be signed in to change notification settings - Fork 392
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
Size limitation on very long grid (the limit is different depending on the browser) #489
Comments
Hi, I'm having the very same issue. I believe it is related to the max-height of the grid of roughly 10k pixels. |
Found it... https://github.com/ManifestWebDesign/angular-gridster/blob/master/src/angular-gridster.js#L1707 This limits it to 9999 pixels. Increasing this value to something larger fixes our problem. |
anx-ckreuzberger
added a commit
to anx-ckreuzberger/angular-gridster
that referenced
this issue
Feb 19, 2019
anx-ckreuzberger
added a commit
to anx-ckreuzberger/angular-gridster
that referenced
this issue
Feb 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I've some trouble to resize gridster's items when they reach a certain size (85 rows in my case).
As you can see in the jsfiddle bellow, it's impossible to make the first item longer. Despite the fact that I increased
maxRows
to a very large number.http://jsfiddle.net/ax21efbd/4/
I've also tried to make smaller blocks, to see if it depends of the size in pixel or of the number of rows. And my conclusion is that, with smaller blocks, the limit is reach with a higher number of row, but there is still a limit/problem.
Did I miss something ? Does it happened to someone else ?
Thank you very much for your help.
(Sorry for any spelling mistakes. English is not my native language.)
Update 1
I just found out that the behaviour depends on the browser :
On Chrome: items can't exceed 85 rows
On Firefox: items can't exceed 87 rows
On Safari: items can't exceed 124 rows
The text was updated successfully, but these errors were encountered: