Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Hardware acceleration and fingerprinting

Offen
  • Stimmt etwas nicht?
#896 2 Kommentare 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
30/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
javascript
Bereich
api, audio-video-rtc

Rechercherichtung

Beginne mit dem Abschnitt zur Hardwarebeschleunigung der WebCodecs-Spezifikation und dem Beispiel für VideoEncoder.isConfigSupported, und überprüfe anschließend den verknüpften Bugzilla-Bericht sowie die beiden bestehenden Kommentare. Das Issue ist abgeschlossen, wenn das Verhalten von hardwareAcceleration unter Fingerprinting-Einschränkungen und das beobachtbare Ergebnis für Autoren vereinbart und spezifiziert sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

I just filed a bug on Bugzilla but what Firefox is doing is spec compliant, so I wanted to raise the issue here too.

Background

I'm making a website that heavily utilizes WebCodecs. I need to determine the encoding codec and always want to use hardware encoding (when available) as battery life is more important than fidelity (conference call).

  1. Loop through all codecs in order of network efficiency: av1, vp9, hevc, h254, vp8, etc
  2. Check if the browser supports hardware acceleration, if so return it.
  3. Repeat the loop but this time with software acceleration.

I'm using the hardwareAcceleration: "prefer-hardware" field to determine if hardware acceleration is supported. Here's an example of one of the checks:

VideoEncoder.isConfigSupported({
    codec: "av01.0.08M.08",
    width: 1280,
    height: 720,
    hardwareAcceleration: "prefer-hardware",
}).then(console.log)

Here's a little modal I created to visualize the process and the results on my M2 laptop and Chrome.

Image

Problem

Here's what Firefox reports:

Image

Ignore the partial support for video capture (MediaStreamTrackProcessor polyfill).

The problem is that Firefox is reporting hardware acceleration for AV1, VP9, etc. So my encoder will naively select one of those codecs and suddenly my CPU is on fire.

My guess is that Firefox is ignoring the hardwareAcceleration field to avoid fingerprinting. Here's the relevant section in the specification:

If a User Agent does not implement [media-capabilities] for reasons of fingerprinting, they SHOULD ignore the HardwareAcceleration preference

Proposed

If the browser won't respect hardwareAcceleration because it can be used for fingerprinting, then the browser should return an error somehow. I don't think the browser should silently ignore important configuration values without feedback.

If I knew that Firefox doesn't allow probing for hardware acceleration, then I would use H.264 because hardware acceleration is very common and easier on the CPU. Then I could also report hardware acceleration as "unknown" and maybe show a modal explaining why performance might be poor.

My suggestions:

  1. Don't return hardwareAcceleration in the config returned by isConfigSupported. Unfortunately, this isn't quite correct, as hardwareAcceleration is supported but only as a hint.
  2. Add "require-hardware" and "require-software" as options, throwing an exception (or returning false?) if they are used on browsers that care about fingerprinting.
  3. Firefox pls allow me to detect hardware acceleration. Otherwise I can't use newer codecs for fear of melting silicon.

I think #2 is the best option. It's kind of strange that Chrome returns isConfigSupported=false when "prefer-hardware" is used. If it's just a hint, like the "prefer" implies, then it should always return true if either software or hardware encoding is available... right?

Vorherrschende Sprache
HTML
Sterne
1.3k
Forks
190
Ø Merge
1 T. 4 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus w3c/webcodecs

Alle Issues in w3c/webcodecs

Ähnliche Issues

Weitere Issues zu Backend & API Design

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.