Issue 18466

Fullscreen map button using Chrome

18466
Reporter: donald hobern
Assignee: hoefft
Type: Bug
Summary: Fullscreen map button using Chrome
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2016-05-13 06:12:05.131
Updated: 2017-10-10 15:30:37.734
Resolved: 2017-10-10 15:30:37.713
        
        
Description: On Firefox, the maps on species/dataset/country pages include a fullscreen control button below the + and - zoom controls.  This does not appear using Chrome.

The decade slider doesn't seem to work at the moment on my Chrome browser either.

Chrome: Version 50.0.2661.94 m
Windows 10

*Reporter*: Donald Hobern
*E-mail*: [mailto:dhobern]]]>
    

Attachment screenshot-1.png



Author: hoefft
Comment: That doesn't sound good. The full screen thing is not supported on all browsers as not all browsers support it. The old version didn't either. But Chrome should. As for the missing time slider I suspect Chrome has changed the way it handles flexbox. Either way it should be fixed. I'll start by seeing if I can reproduce it. Thanks.
Created: 2016-05-13 11:33:22.356
Updated: 2016-05-13 11:33:22.356


Author: hoefft
Created: 2016-05-13 11:55:18.125
Updated: 2016-05-13 11:59:40.581
        
I have just tried on Windows 10 in chrome version 48 and version 50.0.2661.102
Both fullscreen and decade slider works fine on my windows image.

Internet explorer however doesn't support it. If memory serves me well this was also the case for the previous version. That said it should be possible to get it working on ie10 and above. But ie doesn't support standard fullscreen api.

For the initial release the map was tested in:
* firefox, chrome, opera on mac and windows.
* safari on mac
* ie 8+9+10+11 on windows
* chrome + safari on ios
* chrome on android

Not all functionality was available on all platforms but there was no known regressions. But with browser updates it might no longer be the case that it works as expected.
    


Author: hoefft
Comment: To fix it I need to reproduce it. Maybe an actual windows machine would be useful. The virtual version is frustratingly slow anyhow. SauceLabs could also be an option.
Created: 2016-05-13 11:57:36.461
Updated: 2016-05-13 11:57:36.461


Author: donald hobern
Comment: Can show you when I'm back in the office next week.  Donald
Created: 2016-05-16 01:32:15.894
Updated: 2016-05-16 01:32:15.894


Author: hoefft
Created: 2016-05-16 13:10:39.461
Updated: 2016-05-16 13:11:59.764
        
Let's do that. You could also open the developer console and send me the stacktrace if there is one?
At times these browser differences are insanely annoying.