You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One observation: this only has happened once, but when I was searching for the "Life and Letters of Emily Dickinson" on Leo Stein's card, when I clicked the card where the event took place it highlighted the event but it was soooo far up at the top of the screen that at first I couldn't see it was highlighted at all. I tried to take a screenshot of it:
--> if you look up at the very top there's the pale blue highlight but I almost missed it. I think this has something to do with the fact that the borrow is the FIRST on the card? I tried again with other books that appear first on the card and this happened every time. Not a big deal at all, but worth noting if you guys know how to fix it. (Or maybe it's just my small laptop screen's fault?)
@jkotin sorry I didn't write testing notes. Here's a specific example so you can compare the behavior between production and test and confirm this is fixed:
One observation: this only has happened once, but when I was searching for the "Life and Letters of Emily Dickinson" on Leo Stein's card, when I clicked the card where the event took place it highlighted the event but it was soooo far up at the top of the screen that at first I couldn't see it was highlighted at all. I tried to take a screenshot of it:
--> if you look up at the very top there's the pale blue highlight but I almost missed it. I think this has something to do with the fact that the borrow is the FIRST on the card? I tried again with other books that appear first on the card and this happened every time. Not a big deal at all, but worth noting if you guys know how to fix it. (Or maybe it's just my small laptop screen's fault?)
Originally posted by @clmahoney in #264 (comment)
Both @rlskoeser and @thatbudakguy looked into this problem, but typical css solutions don't apply here because we're dealing with table elements.
The text was updated successfully, but these errors were encountered: