Showing questions tagged: Show all questions
  • Archived

Firefox vers 91.10esr(64bit):-"cannot load M3U8:levelLoadTimeOut"

Hi!, recently i have been having this browsing problem whenever I open the news website at https://www.cgtn.com/channel/documentary. The site wont load and error is shown… (read more)

Hi!, recently i have been having this browsing problem whenever I open the news website at https://www.cgtn.com/channel/documentary. The site wont load and error is shown- "cannot load M3U8:levelLoadTimeOut". Have tried numerous times but failed to load. However other web sites have no problem and prior to this I am able to surf at all times. What must I do to get back the browsing? Any help is appreciated. Thanks

Asked by xxmanreturns 1 year ago

Last reply by cor-el 1 year ago

  • Archived

Some pages not loading in 91.10.0esr

I use Firefox on Linux Debian 11 (Bullseye). After a recent automatic update to Firefox 91.10.0esr, some websites will not load (just sit with a blank page, showing flick… (read more)

I use Firefox on Linux Debian 11 (Bullseye). After a recent automatic update to Firefox 91.10.0esr, some websites will not load (just sit with a blank page, showing flicking loading symbol). Examples are ocado.com and abelandcole.co.uk. I have tried all the usual things to fix, including, switching off VPN, clearing cookies and caches, running in safe mode, all with no success. Both sites run fine in Vivaldi and Brave. I have eventually got the pages to load by disabling IPv6 in Firefox. Clearly there is a problem with 91.10.0esr. I'm not sure whether the workaround of disabling IPv6 might cause other problems or weaken security or privacy?

Asked by Chris 1 year ago

Last reply by jonzn4SUSE 1 year ago

  • Solved
  • Archived

cannot fast forward or back while playing mp3 file

Using Firefox 100.0.1. Debian Linux. Dell 1525 with 4G ram. When playing a certain mp3 file in the browser, if I use the arrow keys, or the mouse, to skip forward or bac… (read more)

Using Firefox 100.0.1. Debian Linux. Dell 1525 with 4G ram.

When playing a certain mp3 file in the browser, if I use the arrow keys, or the mouse, to skip forward or back, there is no response, but the audio stops playing for a period of time, then, finally it starts playing again at the spot it was before.

This does not happen with this file in Chrome, or in VLC. Also, with other mp3s it does not happen in Firefox.

I finally got it to work by converting the file to ogg vorbis, but this is not something I want to make a practice of..

I imported the file back into Audacity, and re-exported it as an mp3. Same result.

Weird... Any ideas?

Thanks,

Asked by gophild 1 year ago

Answered by jonzn4SUSE 1 year ago

  • Archived

Commit view on GitHub with FireFox broken

Hello, First let me thank Mozilla again for a great experience. I've been using Firefox as my main browser for many years and since some time I also started supporting Mo… (read more)

Hello, First let me thank Mozilla again for a great experience. I've been using Firefox as my main browser for many years and since some time I also started supporting Mozilla financially with whatever little I can with recurring payments. To the problem: since some time patch / commit view on HitHub with Firefox is broken. I guess many @mozilla have github accounts so you can open and read https://support.github.com/ticket/1318472 but to summarise: my first entry there was: ``` When viewing Linux kernel style Pull Requests on GitHub, using Firefox, TABs are displayed as 4 spaces, which is confusing, since the default is 8 spaces, which is also what is displayed in chrome and chromium. E.g. https://github.com/thesofproject/sof/pull/4747/commits/e9cc9312841a9329797b0b676335c8cb1a0dc779 ``` then a screenshot (attached) and a clarification to it: ``` As you can see there the patch area between lines 238 and 245 is wrongly indented by 4 spaces, whereas areas above and below are correctly indented by 8 spaces. ``` Then more: ``` No, space isn't used for indentation in that code. They can download raw code and verify, I'm sure they know how to do that. Why don't they just reproduce that themselves? Start Firefox, navigate to any PR commit like https://github.com/thesofproject/sof/pull/4884/commits/b19a64df2c2fcd63d7407ef500fd3312287c8995 and click arrows above and below the diff to display surrounding code. Then navigate to or download the raw patch https://github.com/thesofproject/sof/commit/b19a64df2c2fcd63d7407ef500fd3312287c8995.patch to see TABs used everywhere. Should be very easy to verify. ``` and their last reply was ``` From a technical standpoint this is not a regression. It's a problem with the way firefox interprets the combination of the tab-size css and the particular markdown we use for our diffs.

After reviewing the Issue in more detail there it has not been prioritized and will most likely not be addressed in the near future. ``` This is a deal-breaker for me. I spend hours daily reviewing GitHub pull requests. And I'd really not want to use a different browser just because of this... Please help! Thanks Guennadi

Asked by lyakh 2 years ago

Last reply by lyakh 1 year ago