Closed Bug 1798067 Opened 2 years ago Closed 1 year ago

Add telemetry for HDR capability based on per-platform capability detection

Categories

(Core :: Graphics, task)

task

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox109 --- fixed

People

(Reporter: bradwerth, Assigned: bradwerth)

References

Details

Attachments

(3 files)

It would be useful to know how many of our clients are capable of viewing HDR video. This telemetry should be emitted infrequently because it will not change regularly. So instead of including it in the general metrics ping, we could define a graphics-specific metrics ping at a longer cadence.

There are at least two ways to signal HDR capability:

  1. Emit telemetry per-platform based on hardware detection customized to that platform.
  2. Emit telemetry for all clients, based on our reported support for HDR video, which is informed by Option 1.

Option 2 is what is being proposed by this Bug. Bug 1751217 caused macOS to report HDR via matching of video-dynamic-range: high, which is checked by YouTube. So emitting telemetry based on matching this value will magically capture other platforms when and if they start reporting HDR capabilities this way.

Currently, the Windows-specific HDR telemetry in Bug 1514840 does not affect the matching of video-dynamic-range: high. If it ever does, then this mode of emitting capability telemetry will start to include results for Windows clients.

Changed my thinking on this. We already collect telemetry about HDR usage via video_hdr_play_time_ms. What we need is telemetry that shows the addressable user base -- measuring the possibility of HDR. So this Bug will abstract the per-platform HDR capability check into a new enum, hdr_capable.

Summary: Add telemetry for HDR capability as determined by matching `video-dynamic-range: high` → Add telemetry for HDR capability based on per-platform capability detection
Attachment #9302137 - Attachment description: WIP: Bug 1798067 Part 1: Add SupportsHDR to gfxPlatform, refactor macOS to use it. → Bug 1798067 Part 1: Add SupportsHDR to gfxPlatform, refactor macOS to use it.
Attachment #9302138 - Attachment description: WIP: Bug 1798067 Part 2: Implement gfxWindowsPlatform::SupportsHDR. → Bug 1798067 Part 2: Implement gfxWindowsPlatform::SupportsHDR.
Pushed by bwerth@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1b59437ed62b
Part 1: Add SupportsHDR to gfxPlatform, refactor macOS to use it. r=gfx-reviewers,lsalzman
https://hg.mozilla.org/integration/autoland/rev/f87001406f29
Part 2: Implement gfxWindowsPlatform::SupportsHDR. r=jgilbert,gfx-reviewers
https://hg.mozilla.org/integration/autoland/rev/dba34dc9a166
Part 3: Emit telemetry for gfx.supports_hdr alongside other gfx telemetry. r=gfx-reviewers,nical
Pushed by bwerth@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/324b83e29ae6
Part 1: Add SupportsHDR to gfxPlatform, refactor macOS to use it. r=gfx-reviewers,lsalzman
https://hg.mozilla.org/integration/autoland/rev/fad1872ea963
Part 2: Implement gfxWindowsPlatform::SupportsHDR. r=jgilbert,gfx-reviewers
https://hg.mozilla.org/integration/autoland/rev/fd40e36100cc
Part 3: Emit telemetry for gfx.supports_hdr alongside other gfx telemetry. r=gfx-reviewers,nical
Regressions: 1803034
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
Flags: needinfo?(bwerth)
Duplicate of this bug: 1664855
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: