[desktop] Bugs logged by Desktop Release QA in the last 7 days

Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/wecwaxz. Bugs logged by Desktop Release QA in the last

Re: How to generate compatible firefox for all versions of linux system?

On Tue, Dec 10, 2019 at 10:54:39PM -0800, acnatar...@gmail.com wrote: > Hi all, > > I had built a firefox on ubuntu 16.04 with GCC 5.4.0 and Glibc 2.23 from > Mozilla-central. Exported the package using "./mach package". > > firefox version 72.0a1.en > > When I try to launch the exported

Re: How to generate compatible firefox for all versions of linux system?

According to this page [1], the current minimum version of gcc required to build Firefox trunk is 7.1. If you need to build with gcc 5.4, you may need to build an older release or esr branch rather than current trunk. I don't know if the compiler requirements are documented on a per release basis

Re: Intent to prototype: Character encoding detector

On Mon, Dec 2, 2019 at 2:42 PM Henri Sivonen wrote: > 1. On _unlabeled_ text/html and text/plain pages, autodetect _legacy_ > encoding, excluding UTF-8, for non-file: URLs and autodetect the > encoding, including UTF-8, for file: URLs. > > Elevator pitch: Chrome already did this unilaterally. The

PSA: Dispatching background tasks just got easier!

Hello! Now that Bug 1584568 just landed I wanted to mention the new background thread pool for general purpose and blocking IO runnables. Existing one-off threads, as well as new jobs that you may want to run async in the background, can go to the new background thread po

Re: How best to do async functions and XPCOM?

On 12/10/19 3:31 PM, Kris Maglione wrote: In what way is dom::Promise annoying to use from C++? The one thing I know about that's pretty annoying is if you receive the promise from someone else and want to add reactions to it. PromiseNativeHandler kinda works, but then you get JS::Values and