Archives Canada links (French, contact us etc.) don't appear in mobile version
|Assignee:||Jesús García Crespo||% Done:|
|Target version:||Release 2.1.0|
|Google Code Legacy ID:||Tested version:||2.0.0, 2.0.1|
I mentioned this in a comment in #5590, but that issue is primarily about Dominion so I thought it might be buried. In particular I wanted to flag the inability (via mobile) to choose the French interface of Archives Canada.
The Archives Canada issue is similar to part of what was reported in #5590, but in this case, playing with the Chrome element inspector, I think div.row is colliding with div.span12
#3 Updated by Dan Gillean over 8 years ago
- Priority changed from Medium to High
Bumping this to high, because making sure that the option to change the application interface language is included is essential before ArchivesCanada goes live.
Tim, FYI - we will be making the language option and some of the others available, but we may not make the login button visible in mobile - while the Bootstrap theme provides some native responsiveness, we have not built nor rigorously tested 2.x for description/digital object upload/administration/etc via mobile - the first goal of our mobile work is to make sure that end users can browse the application.
Thanks again for reporting this - I've reproduced it on my Android (Jelly bean) phone using Dolphin Browser as well.
#4 Updated by Dan Gillean over 8 years ago
- File AtoM-header-960px.png added
This actually ties in with general responsive issues in both themes. E.g., if the browser width is reduced to 960px or less, the browse button separates from the search box in the header, the search box occupies the entire width of the header (nearly), and the login/main menu icons are no longer accessible. Screen shot attached. A client has noted similar issues in a custom theme:
The login button does not appear at the top of the page if the screen resolution is <=1280 px wide.
I was using a 24” monitor with a native resolution of 1920x1080, using both Firefox 26.0 and Chrome 32.0; interestingly, the problem didn’t appear in IE 8.0