Bugzilla

Sure -- part 2 of your understanding is the part that's not-quite-correct -- the patch that landed to fix things here **only reenabled the library for release configurations**,  and it left the library disabled for Nightly (and "early beta" i.e. first half of each beta cycle) configurations.

if you click through to see the code change in comment 8, you can see it has:
```
 - name: media.hls.enabled
[...]
+  value: @IS_NOT_EARLY_BETA_OR_EARLIER@
```

The default `value` of that about:config pref evaluates to `true` in official release builds (e.g. 132.0.2,), and it evaluates to to `false` in Nightly-branded builds (e.g. current 134.0a1) -- i.e. turning off the feature.  (But importantly, it'll still evaluate to `true` for v134 **release** when we release Firefox 134 (and subsequent releases), because that variable is controlled by the build configuration, not by the version number.)

The idea (I think) is that we can leave this feature experimentally disabled, only-in-Nightly-and-early-beta (for now), so that we can watch for other bug reports from Nightly users and find out what other sites (if any) might have the same sort of breakage; and in the meantime, release users won't be subject to any potential breakage.

Sure -- part 2 of your understanding (specifically "Mozilla reverted the patch that disabled the HLS library")  is the part that's not-quite-correct -- the patch that landed to fix things here **only reenabled the library for release configurations**,  and it left the library disabled for Nightly (and "early beta" i.e. first half of each beta cycle) configurations.

if you click through to see the code change in comment 8, you can see it has:
```
 - name: media.hls.enabled
[...]
+  value: @IS_NOT_EARLY_BETA_OR_EARLIER@
```

The default `value` of that about:config pref evaluates to `true` in official release builds (e.g. 132.0.2,), and it evaluates to to `false` in Nightly-branded builds (e.g. current 134.0a1) -- i.e. turning off the feature.  (But importantly, it'll still evaluate to `true` for v134 **release** when we release Firefox 134 (and subsequent releases), because that variable is controlled by the build configuration, not by the version number.)

The idea (I think) is that we can leave this feature experimentally disabled, only-in-Nightly-and-early-beta (for now), so that we can watch for other bug reports from Nightly users and find out what other sites (if any) might have the same sort of breakage; and in the meantime, release users won't be subject to any potential breakage.