-
Notifications
You must be signed in to change notification settings - Fork 29
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
Using significantly more column space (overlap) when used with history-graph card (affecting zoom factor on mobiles) #52
Comments
@bcutter, do you have transitions enabled? If so, you might see if disabling them cures the problem. |
You´re right, this issue only appears when having a transition enabled. So hard to decide... as described here #41 (comment) you can´t have em all, like "a history-graph of type 'laying bars' without any transition". Thomas needs to have a look into this as something´s just really mixed up here. |
It's possible that 1.9.1 fixes this. |
Unfortunately no, it doesn´t. You haven´t found the root cause for this yet :-( |
Please try release 1.9.3 |
v1.9.3 rocks (so do you)! Fixed everything I mentioned earlier in this issue. Thank you. |
In addition to #41 the rare types of history-graph cards working with state-switch (the ones with a X and Y axis) result in the history cards using more space than allowed in their column.
I discovered this when using the mobile (smaller screen).
Without state-switch:

With state-switch applied to history-graph card:

Please notice the automatically changed zoom factor. So the hole view is malformed on the mobile screen.
On a second view the zoom factor remains, but the graphes are cut (overlapping screen) instead.
state-switch really has some significant issues with history-graph card!
The text was updated successfully, but these errors were encountered: