mdn / mdn/browser-compat-data

api.VideoPlaybackQuality.totalVideoFrames - totalVideoFrames is 0 in Firefox and Safari

Open
#21,484 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Browser compatibility shows that totalVideoFrames is supported on firefox and safari but for both browsers it returns 0. Chrome and edge works. The video is visually moving. For firefox mozPaintedFrames does work but is deprecated so I rather use the same object for each browser.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

I expected the value to go up with each function call.

Did you test this? If so, how?

Tested this while running playwright tests locally on latest chrome, firefox, edge and webkit versions.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/VideoPlaybackQuality/totalVideoFrames

MDN metadata
MDN page report details
  • Query: api.VideoPlaybackQuality.totalVideoFrames
  • Report started: 2023-12-05T12:26:51.628Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MDN URL and the browser-compat-data entry for VideoPlaybackQuality.totalVideoFrames, then reproduce the reported behavior in the latest Chrome, Firefox, Edge, and WebKit versions as described. Done means the compatibility data accurately reflects confirmed browser behavior, with supporting evidence for any change.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.