Summary: | progress bar on "Media Player" widget don't reset correctly in Youtube Music | ||
---|---|---|---|
Product: | [Plasma] plasma-browser-integration | Reporter: | angelo <elpepechingon> |
Component: | Firefox | Assignee: | Kai Uwe Broulik <kde> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | kdedev |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
angelo
2024-06-28 07:14:03 UTC
Thank you for the bug report. I'm not able to reproduce this with Firefox in either Solus or Kubuntu or KDE Neon To clarify, I was looking at the progress bar in the browser itself Plasma integration 1.9.1 I tried with a browser profile that has no addons other than Plasma Integration (Kubuntu, Neon), as well as one (on Solus) that has quite a few (including YouTube Enhancer) To make sure we're talking about the same thing, are you looking at the progress bar in the browser or a widget or something else? Ideally, if you can get a screen recording of the behavior, that will help us narrow things down. I was talking about the media player widget, sorry if I wasn't clear enough. Here's a videos of the bug: https://streamable.com/ammdwi Thanks for clarifying, and for the video. It clearly shows what you're describing. I was able to reproduce the bug in a different way on Solus. The problem is intermittent. - Firefox profile with no addons except Plasma Integration - Media Player widget on the desktop - Loaded a YouTube playlist https://www.youtube.com/watch?v=kXYiU_JCYtU&list=PLyORnIW1xT6wFALM5dZlkFhOULbToFok3&index=1 - Used the mouse to click on the progress bar in the browser window and skip ahead in the video Expected: The progress bar in the widget matches the one in the browser Observed: The progress bar sometimes doesn't move ahead to the new position like the one in the browser does I tried vimeo.com and wasn't able to reproduce the problem there, so it seems the problem might be with how either the YouTube API is sending data or how the widget is interpreting that data. |