Inconsistent styles and responsive design issues in My Account grids
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.10 |
Fix Released
|
Medium
|
Unassigned | ||
2.9 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Evergreen version: all
This bug addresses two style issues in the My Account screens.
The holds history page uses different styles than the holds, items out, and check out history pages. The styles on all four pages should be consistent.
In addition, the check out history and holds history pages do not display correctly on small screens. This issue is caused by CSS that was used to reposition the table headers to display along the side when these screens are retrieved on small screens.
The items out screen and check out history tables share the same class, even though they use different table headers. There is an #acct_checked_
The holds history table has no class assigned to it. Therefore, no adjustments are made when it displays on a small screen.
We need to make use of the #acct_checked_
Changed in evergreen: | |
status: | New → Confirmed |
description: | updated |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Work-in-progress branch at http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ kmlussier/ lp1614807- my-account- screen- fixes.
I ultimately decided to forego doing a small-screen adjustment for the Holds History screen that matches the other interfaces. With the absence of a checkmark row, there was no separator that clearly defined where one title stopped and another one began. I'm sure there is a good way to handle it, but after spending some time on the problem, I realized I don't have the tuits to do it right now. For a future release, it might be a good idea to re-evaluate how we handle the responsive design for all four of these My Account interfaces, but that's the topic for another bug.
I'm hoping to address some spacing issues before adding a pullrequest tag to this bug.