| Summary: | Play/pause not always working reliably on tunein.com | ||
|---|---|---|---|
| Product: | [Plasma] plasma-browser-integration | Reporter: | Or Schiro <orschiro> |
| Component: | Chrome | Assignee: | Kai Uwe Broulik <kde> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Or Schiro
2018-09-03 13:48:50 UTC
I can confirm it doesn't work on this site. Apparently there is also a "video" element on that page which it ends up controlling. Controlling the audio player manually from developer console works. An approach I thought about could be to ignore signals from <video> elements that aren't part of the DOM since you cannot see them anyway. However, Spotify uses a <video> (rather than <audio>) for playing its music :( Dear Kai, I found this [1] website to also not support the playback buttons on my keyboard. Can you confirm? What's the best procedure to track sites that don't work properly? Is it good to keep them all in one place (here), or better to open a new ticket for each page? Yours, Robert [1] http://cinemix.radio.net/ Thanks for your feedback! It's best if each issue is filed in a separate ticket as it is likely to be a different root cause every time. The cinemix site uses JavaScript "Audio" instead of HTML5 <audio> tags which we currently don't support. It is not possible to pass JavaScript variables from the website to the extension script. The content script can access the DOM of the website and as such extract <audio> and <video> tags but I haven't found a way yet to pass pure-JS audio/video players around. Thanks, Kai! For further reference: https://bugs.kde.org/show_bug.cgi?id=398261 |