Twitch fails to load m3u8 on nightly 161
Categories
(Core :: Privacy: Anti-Tracking, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr153 | --- | unaffected |
| firefox159 | --- | unaffected |
| firefox160 | --- | unaffected |
| firefox161 | --- | disabled |
| firefox162 | --- | fixed |
People
(Reporter: bugzilla.agenda865, Assigned: timhuang)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 external file)
Steps to reproduce
Load a twitch stream on Nightly build 2026-11-02-22-14-20
(This was previously working on build 2026-11-02-09-39-42)
Actual results
Any twitch stream, the network tab in dev tools shows that m3u8 files fail to load
Expected results
Stream should play normally.
Media profiler
https://share.firefox.dev/4iV0SVf
This does not seem to be an issue on kick.com, m3u8 works. I have verified that this is not a network issue, as the same stream loads properly on firefox stable.
Comment 3•16 days ago
|
||
Thanks for the report! Does the stream load if you turn off Enhanced Tracking Protection for twitch.tv (shield icon)? Are you using Standard or Strict? What status or blocked reason does the failing m3u8 request show in the Network tab?
| Assignee | ||
Comment 4•16 days ago
|
||
I can reproduce the issue in ETP Strict mode.
The issue is caused by enabling the content classifier on Nightly. The content classifier doesn't get a top-level URI for worker requests. As a result, ttvnw.net requests made from a web worker on twitch.tv get blocked, which shouldn't happen because they are in the same entity.
| Assignee | ||
Comment 5•16 days ago
|
||
This patch moves the worker fallback in
UrlClassifierCommon::CreatePairwiseEntityListURI into a new
GetTopWindowURIWithFallback helper and uses it when building a
ContentClassifierRequest. Worker requests have no top window, so the
classifier passed an empty source to the engine and $domain= options were
ignored. For example, ttvnw.net loaded by a worker on twitch.tv was
blocked despite its ~twitch.tv exclusion.
Updated•16 days ago
|
Updated•16 days ago
|
Comment 6•16 days ago
|
||
Set release status flags based on info from the regressing bug 2053164
Comment 9•14 days ago
|
||
| bugherder | ||
Comment 10•14 days ago
|
||
The patch landed in nightly and beta is affected.
:timhuang, please make an uplift decision for beta:
- For beta, nominate the patch for beta uplift approval if the fix should be included in this release, or set
status-firefox161towontfixif the fix can wait for the next release.
Uplift requests can be submitted from Lando: D339251.
See Requesting an Uplift for documentation on how to request an uplift.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 11•14 days ago
|
||
This doesn't affect beta because the issue occurs only on Nightly.
Updated•14 days ago
|
Description
•