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

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 firefox from another ubuntu machine with same config ubuntu 16.04, GCC 5.4.0 I was

Re: [IMPORTANT] Submit your PI Requests and technical documentation for Firefox 73 QA feature testing by Dec 13

Hi, This is a reminder that the deadline for PI Requests and technical documentation for Firefox 73 is this Friday, December 13th. Please log your PI Request tickets as soon as possible, and provide the required technical docs. Thank you, Tom On Wed, Dec 4, 2019 at 6:59 PM Tom Grabowski

Re: How best to do async functions and XPCOM?

Thanks to all who replied, including Kris whose reply seems to have not made it back to the list. As per usual when I ask for help I've been immediately distracted by something more urgent and not got back to the problem at hand. :-/ As some pointed out this would be a lot easier if I was

Re: How best to do async functions and XPCOM?

On Sun, Dec 08, 2019 at 11:40:52PM -0500, Joshua Cranmer  wrote: The problem with MozPromise is that it doesn't integrate well if you use XPIDL interfaces, so you have this annoying issue that if you want to use XPIDL integration, you have to use mozilla::dom::Promise, which is annoying to

Re: Intent to Prototype: Constructable Stylesheet Objects

> > DevTools Bug: TBD what, if anything, is needed. > In principle, if Constructable Stylesheets are included in the same APIs used to get and listen to regular stylesheets, DevTools should support them out-of-the box. An overview of the continued API support to handle stylesheets in

Intent to prototype and ship: IDBTransaction.commit

*Summary*: IDBTransaction objects will gain a commit() function that explicitly marks a transaction as not accepting further requests. Currently, IndexedDB only commits a transaction after all associated requests have had their completion event handlers executed, and no new requests have been

Re: How best to do async functions and XPCOM?

Also sprach Joshua Cranmer: > The problem with MozPromise is that it doesn't integrate well if you use > XPIDL interfaces, so you have this annoying issue that if you want to use > XPIDL integration, you have to use mozilla::dom::Promise, which is annoying > to use from C++. A third wrinkle,

Re: Local Windows builds to use clang-cl by default

On Tuesday, 21 August 2018 20:42:44 UTC+1, David Major wrote: > Hi, > > Local Windows builds will use clang-cl and lld-link by default as of > bug 1483835. This will make your builds match what has been shipping > on Nightly for the last several weeks, and help avoid the occasional > MSVC

Re: How best to do async functions and XPCOM?

On Fri, Dec 06, 2019 at 11:20:12AM +1300, Geoff Lankow wrote: Hi all I'm redesigning a bunch of Thunderbird things to be asynchronous. I'd like to use Promises but a lot of the time I'll be far from a JS context so that doesn't really seem like an option. The best alternative I've come up

Re: Proposed W3C Charter: Web of Things Working Group

Hi, I'd like to provide Mozilla IoT team feedback on this charter, the content of which has already been modified slightly based on our earlier feedback to the Working Group during the drafting stages. We are happy overall with

Re: Intent to prototype: Character encoding detector

On 12/9/19 6:24 AM, Henri Sivonen wrote: Good point. I'll use tentative WPTs for end-to-end automated tests. Thank you! -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform