-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add hover cards #670
Comments
Thank you, those both look like issues. 👍 I've also noticed that in some cases, there is too much padding below the list of properties in the hover card for an entity list. For example, if you hover over the "basic" entity list here: https://test.getodk.cloud/#/projects/414/entity-lists |
I didn't have a chance to make these changes today, but I'll do so soon. |
Yes, good catch! It should. I'll make that change tomorrow. The issue has been closed because we finished code review. That means that you can now view it on staging in addition to the QA server. However, I still need to make the changes for the issues described above. Let me know if you see any other issues involving hover cards. |
This should now be fixed. |
@sadiqkhoja mentioned to me yesterday that he was seeing an issue with hover cards:
In other words, if there wasn't enough space for the hover card on either the right or the left of the link, it was being shown partly offscreen. Instead, we want to show the hover card above or below the link if there isn't space for it on the right or left. getodk/central-frontend#1097 was merged to address this issue, and the issue should now be fixed. Let me know if you ever notice a hover card being shown offscreen. |
We're also tracking another issue with hover cards. It definitely affects hover cards for forms and may affect other hover cards as well. The issue is: In a hover card for a form, if the text in the second column is shorter than the text in the first column (i.e., if the form version is short), then the hover card will widen to fit the full width of the form name. The problem is that hover cards are not supposed to become arbitrarily wide. The form name is supposed to truncate if it's too long. I'm planning to fix this issue tomorrow. |
This should now be fixed.
I think these are the last two things that need to be fixed. |
That one is actually by design. If the list of properties doesn't fit, it will be visible up until the very edge of the hover card. In the release criteria, there's a screenshot along those lines that you can see.
This should now be fixed. I haven't updated the QA server yet, but you can see the fix on staging. I'll update the QA server soon as well.
I actually wasn't able to reproduce this issue on my machine, perhaps due to differences in fonts. However, I made some changes that I'm hoping has addressed this. That change can be seen on staging.
This should now be fixed on staging. The issue was due to property names that contained a hyphen. |
After editing an entity with a long name, the hover card in submission detail page is broken (wrong width of property name, entered values are show beyond the hover card. Steps to reproduce:
|
I personally think it's OK. Maybe it's even a good thing, as it's a signal that the page is out-of-date. This question also came up during code review, and I wrote some comments about it here.
I was able to reproduce this, and we should have a fix ready soon. Since we put out the release yesterday, I filed a new issue to track this bug: #854. |
Tested with success! |
See the story in the release criteria.
The text was updated successfully, but these errors were encountered: