this post was submitted on 10 Jul 2023
2 points (100.0% liked)

Firefox

7 readers
37 users here now

The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.

You can subscribe to this community from any Kbin or Lemmy instance:

Related

Rules

While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.

Rules

  1. Always be civil and respectful
    Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.

  2. Don't be a bigot
    No form of bigotry will be tolerated.

  3. Don't post security compromising suggestions
    If you do, include an obvious and clear warning.

  4. Don't post conspiracy theories
    Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.

  5. Don't accuse others of shilling
    Send honest concerns to the moderators and/or admins, and we will investigate.

  6. Do not remove your help posts after they receive replies
    Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.

founded 1 year ago
MODERATORS
yoasif@fedia.io
2
someone in the mood to confirm a bug with me? I think this is new. Seeing this with F115 (on linux) on a clean, new profile. The code didn't change. (fedia.io)
submitted 1 year ago by lovebug@fedia.io to c/firefox@fedia.io
1 comments fedilink hide all child comments
 

someone in the mood to confirm a bug with me? I think this is new. Seeing this with F115 (on linux) on a clean, new profile. The code didn't change.

I used to be able to listen to a big audio file in a streaming manner when loaded from goldfire/howler.js library.

The new behaviour is: firefox will download the whole file before starting to play.

Example: (25MB bytes down will occur) https://jsfiddle.net/ugnt03jo/1/ -> click Run in upper left to render html

  • if you have traffic stats on your system you'll see bytes trickling in the moment you render the html - not when you click the Play button. This is acknowledged in the devtools network-tab after it is fetched in full
  • until fetched in full, the Play button will not stream the audio file

#firefox

top 1 comments
sorted by: hot top controversial new old
[–] lovebug@fedia.io 1 points 1 year ago

https://bugzilla.mozilla.org/show_bug.cgi?id=1842432 is a regression introduced by https://bugzilla.mozilla.org/show_bug.cgi?id=1817997

I wonder how the fix at https://hg.mozilla.org/releases/mozilla-esr115/rev/ea6e2e85fec6

-  if (aDuration.IsInfinite() && aDuration.IsPositive() > 0 && length >= 0 &&
+  if (aDuration.IsValid() && !aDuration.IsInfinite() &&
+      aDuration.IsPositive() && length >= 0 &&

is improving the outcome of that gnarly cpp at https://searchfox.org/mozilla-central/rev/ea550f0d1afaf7747ebd988325ea10cf4e3e4de4/dom/media/ChannelMediaDecoder.cpp#385

my intuition is DownloadProgressed() never gets to fire CanPlayThrough() because ComputePlaybackRate() never comes back with aDuration.isInfinite() negated. Someone with a cpp background explaining that function would help me heaps