Map in full screen doesn't have a 'escape' button.
17819
Reporter: bko
Type: Improvement
Summary: Map in full screen doesn't have a 'escape' button.
Priority: Trivial
Resolution: Fixed
Status: Closed
Created: 2015-09-17 15:28:37.491
Updated: 2017-10-10 11:06:12.304
Resolved: 2017-10-10 11:06:12.285
Description: 1. The same reason we have the "Back to data publishing" block on http://www.gbif.org/country/AT/publishing/countries, while there is a "back" button of the browser. We cannot reliably depend on browsers to provide that "escape hint.
2. We cannot assume most people are like us know one should try "Esc" key.
3. A button to bring the user back to normal view will complete the experience.
We have the hint from Chrome. This is on Opera.]]>
Author: hoefft
Created: 2015-09-22 12:43:15.58
Updated: 2015-09-22 12:43:47.408
I haven't seen any browsers that do not write that you need to press ESC. Both Opera on OSX and Windows states that you need to press escape to leave fullscreen mode. But the user have the option to press "Do not show me this message again". I assume that you have done so [~bko@gbif.org]?
That said, it could be an added option. But it isn't a regression as the previous version doesn't do that either.
If we really want it a solution could be to write it? Or implement a button. But the fullscreen api is a mess, so it might take a while (events are triggered at different times in different browsers).
Author: bko@gbif.org
Created: 2015-09-22 14:36:37.23
Updated: 2015-09-22 14:36:56.483
I am not sure if I ever clicked "Don't show again", but it's a good point to support that we may need a corresponding button to bring the user back to normal view.
It is just a neutral suggestion that IMO will complete the UX, if comparing with itself. It doesn't have anything to do with the current (now previous) implementation of the map widget. If I understand correctly, comparing with the production was only in the last click-around as a criterion that we can decide whether it's a blocker for THAT release. And since it was not, it got filed here.
Usually we evaluate issues periodically and decide whether this gets into the pipeline(sprint). So if it's agreed that this is worth working on, we can put it into the development queue. Or we may choose to close it without any action.
Please correct me if I am wrong on the principles, [~trobertson@gbif.org].
Author: trobertson@gbif.org
Created: 2015-09-22 22:01:54.909
Updated: 2015-09-22 22:01:54.909
I agree it would be nice to have a close button from fullscreen mode like vimeo, youtube etc. do.
However, I also get that the implementation of our fullscreen mode is not ideal given we have to work within the restrictions of what full screen options there are for iframes - i.e. it is inconsistent across browsers. I tend to think our effort would be better spent fixing the mess of the website architecture, so that our maps aren't in iframes at all at which time it should be CSS based and the minimise button can be reliably added.
Author: bko@gbif.org
Comment: Agree that it'll be ideal that the widget is not living in iframes, I forgot to pick the priority in the beginning, but yes, this one is trivial.
Created: 2015-09-22 22:17:44.088
Updated: 2015-09-22 22:17:44.088
