Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛 | Bug]: VideoViewer not working properly on FireFox #9264

Open
Ironicbay opened this issue Dec 27, 2024 · 1 comment
Open

[🐛 | Bug]: VideoViewer not working properly on FireFox #9264

Ironicbay opened this issue Dec 27, 2024 · 1 comment
Labels
A-Client Area: Parsec desktop application A-Web Area: Web-related issue C-Bug Issue related to a bug

Comments

@Ironicbay
Copy link
Contributor

Parsec version tested on:

v3.2.1-a.0+dev

Platforms tested on:

MacOS

Bug description:

Enregistrement.de.l.ecran.2024-12-27.a.14.38.14.mov

Relevant output:

No response

@Ironicbay Ironicbay added C-Bug Issue related to a bug B-Triage Blocker: The issue is awaiting triage labels Dec 27, 2024
@Max-7
Copy link
Contributor

Max-7 commented Jan 3, 2025

It does play but it takes a huge amount of time after clicking the play button for the video to start.

Few things to note:

  • the media is loaded: the file has been loaded to an object ressource URL, the source has been set, the video tag sends the canplay, canplaythrough, loadeddata, basically all the events indicating that it should indeed be able to play the media
  • await videoEl.play() returns instantly without any exception thrown
  • the playing event is sent, indicating that the media is being played
  • I've looked at multiple events which could indicate that something is wrong (error, stalled, suspend, ...). We do get a suspend event but it's before we get the canplaythrough event, which makes sens. Same thing also happens on Chrome.
  • tried to force a call to videoEl.load() to try and reload the video, but it doesn't change anything

The only thing I've noticed is that once the video starts playing, it appears in the volume mixer of my system (in this case shown in XFCE), which is not the case with Chrome.
Screenshot 2025-01-03 113344

@FirelightFlagboy FirelightFlagboy added A-Client Area: Parsec desktop application A-Web Area: Web-related issue and removed B-Triage Blocker: The issue is awaiting triage labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client Area: Parsec desktop application A-Web Area: Web-related issue C-Bug Issue related to a bug
Projects
None yet
Development

No branches or pull requests

3 participants