UI Responsiveness
(UXPROD-828)
|
|
| Status: | Closed |
| Project: | Stripes |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UI Responsiveness |
| Type: | Bug | Priority: | P1 |
| Reporter: | twliu | Assignee: | John Coburn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Sprint: | stripes-force 98, stripes-force 97, stripes-force 95, stripes-force 96 | ||||||||||||||||
| Development Team: | Stripes Force | ||||||||||||||||
| Affected Institution: |
SHL
|
||||||||||||||||
| Epic Link: | UI Responsiveness | ||||||||||||||||
| Description |
|
Problems are identified when access folio on tablets and iPads. Some information is hidden. Some buttons and dropdown lists are not responsive. Story should focus on the following Shanghai Public Library needs for this sprint. FYI John Coburn1. Their top concern is the compatibility of circulation-related functions on mobile devices. It would be awesome if we can solve this part first. |
| Comments |
| Comment by John Coburn [ 17/Aug/20 ] |
|
Dropdowns not closing - I believe we've resolved this issue now with a recent update in dependencies. Continuing to address table displays and general responsive display. |
| Comment by twliu [ 19/Aug/20 ] |
|
John CoburnIs there a site where we can test it? The Shanghai team reported they didn't see it resolved on the current demo site. |
| Comment by John Coburn [ 21/Aug/20 ] |
|
For anyone who might be watching this issue, https://folio-testing.dev.folio.org/ is where the most up-to-date code can be seen. |
| Comment by LSP-刘梦洁 [ 24/Aug/20 ] |
|
Here is the latest test document FOLIO test_10.5in Apple iPad_ 8.21.2020.docx |
| Comment by Khalilah Gambrell [ 25/Aug/20 ] |
|
John Coburn , is LSP-刘梦洁 feedback regarding Invalid date related to this story
|
| Comment by Zak Burke [ 26/Aug/20 ] |
|
Khalilah Gambrell, John Coburn, FOLIO test_10.5in Apple iPad_ 8.21.2020.docx But as I think through this, the polyfills in question are for pluralization rules, relative time format, and display names (country, currency, language). The display glitch here isn't about relative time format, which almost makes me wonder if Chrome-for-iOS suffers from the same bug as Safari, and that this is basically the same as
|
| Comment by John Coburn [ 27/Aug/20 ] |
|
I agree, Zak Burke, I think we do need such a component. I'm not sure iOS Chrome is even free of the issue. |
| Comment by Zak Burke [ 31/Aug/20 ] |
|
John Coburn is correct that Chrome on iOS also suffers from
Should we configure stripes-components to re-export all the react-intl components (do we want them all, or just the date/time related components?) right now so we can code all new work to import from @folio/stripes/components? That would prevent us from accumulating additional debt, though that's probably a minimal concern. Khalilah Gambrell, do we have a sense of the priority of this issue? |