Bug 490134 - Chrome Not Saving Video Player State on Refresh
Summary: Chrome Not Saving Video Player State on Refresh
Status: REPORTED
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Chrome (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-11 23:47 UTC by tommy.mcreynolds
Modified: 2024-07-11 23:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tommy.mcreynolds 2024-07-11 23:47:28 UTC
SUMMARY

When watching anime on aniwave.to, I noticed that my media player (in this case, VidSrc.to) was not saving state between reloads, specificially volume levels. Every time I refrehed the page or clicked on the next episode, the volume would automatically be muted no matter what the player was set to prior to reload. I did some digging and found the Plasma Browser Integration plugin was causing the issue. I disabled the "Enable media controls on:" for the following sites:

https://aniwave.to
https://disqus.com
https://vid2a41.site

This fixed my issues, and now the player remembers my volume levels on reloads.



STEPS TO REPRODUCE
1.  Play media on 9anime.to, or presumably any website that has VidSrc embedded.
2.  Refresh page or select a different video
3. Observe volume levels not being "remembered" between reloads
4. Disable Plasma Browser Integration Extension
5. Refresh page
6. Observe saved volume state between reloads

OBSERVED RESULT

Video is muted every time I refresh or reload the embedded player despite prior volume settings

EXPECTED RESULT

Remember the volume levels between reload

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel Version - 6.6.38-1-lts
KDE Plasma Version:  6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

Wayland version 1.23.0-1
Pipewire version 1.2.0-2

Disabling hardware acceleration did not fix the issue.