-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Visual Bug: Misaligned row dividers #566
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
Well technically the content is misaligned from the dividers... anyways, hopefully someone else has seen this or can enlighten me about the issue. |
Can you give us more information about browser, os etc.? P.S. You should use the newest versions :) try SashiDo! |
hah I'm a fool to forget that! I'm using the latest MacOS with the latest Safari. It's been doing this since I can remember using the "beta" dashboard in Parse.com. Switching to Firefox, the bug is not present. |
SashiDo looks pretty cool, but I already migrated. :( |
No problem :) if you have problems with your app just ping us :) |
Could you provide a _SCHEMA document and sample data that reproduces the issue? Looks like it is Safari specific? |
I'm in a bit of a time crunch now, but I can say that the visual problem occurs on rows that have a String field containing an empty string. Deleting the value resolved the problem for that row! Setting up my app without back4app just for this seems like a hassle. I'll ask them to update their service. 'fraid I'll have to look up how to make a SCHEMA doc for you. But honestly adding an empty string to your dashboard on 1.0.19 with Safari should be a pretty quick test. |
This should be fixed by #731 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm using back4app which hosts version 10.0.14 of Dashboard, but I haven't seen this issue mentioned or addressed on GitHub. I have about 40 columns on this object class, and I don't know which one might be causing it.
The text was updated successfully, but these errors were encountered: