Different media control results on different browsers #777
-
G'day! I've noticed that there's some differences in media display between browsers. I hadn't thought of this before but after reading issue #759, I noticed a report in there and decided to try things. On spectrogram recordings at the bottom, I get varying results. Firefox yields Which I thought was normal and all works. Google Chrome yields: The volume and fullscreen icons seem to be either disabled or obfuscated by an overlay etc - no biggy. Which is interesting with new options! However, Safari yields: Nothing, basically. The play button still exists in the middle of the spectrogram, which is fine, however, no media controls at the bottom. I was pondering the differences and just supposed that browsers do things differently, but the download and (perhaps less-so) playback speed controls might be a nice thing to have. I'm a bit rusty on media webcontrols these days. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi Lloyd - thanks for looking into this. I always appreciate exploring the intricacies of different software functions. You're right that different browsers handle these things differently, and we developers don't really have much control over it unless we want to implement a custom video player plugin. As for Safari, I think what's happening there is that the media controls aren't showing due to some code I implemented a few weeks ago that disables media controls if there are more than 100 detections displayed on the "Recordings" page. (d257b14) This is to reduce lag and overall make the "Recordings" page a lot more usable. So if you want to see what Safari's media controls really look like I recommend taking a look at any of the detections on "Overview" or "Today's Detections" - those will definitely not be affected by my code which disables the controls. Take care, |
Beta Was this translation helpful? Give feedback.
Hi Lloyd - thanks for looking into this. I always appreciate exploring the intricacies of different software functions.
You're right that different browsers handle these things differently, and we developers don't really have much control over it unless we want to implement a custom video player plugin.
As for Safari, I think what's happening there is that the media controls aren't showing due to some code I implemented a few weeks ago that disables media controls if there are more than 100 detections displayed on the "Recordings" page. (d257b14) This is to reduce lag and overall make the "Recordings" page a lot more usable.
So if you want to see what Safari's media controls really look l…