Re: C++ Core Guidelines

2015-10-01 Thread Jonathan Watt
For those who are interested in this, there's a bug to consider integrating the Guidelines Support Library (GSL) into the tree: https://bugzilla.mozilla.org/show_bug.cgi?id=1208262 On 30/09/2015 22:00, Botond Ballo wrote: Hi folks, I wanted to draw your attention to a new project underway in

dialog=1 for window.open from content

2015-10-01 Thread Mike Conley
Hello dev-platform, I'm currently working on bug 1095236 - that's an e10s bug for us failing to open any windows if the features string includes dialog=1 (or dialog=yes). According to [1], setting dialog=1 makes a popup window that removes the min/max/restore buttons, and no "command" menu (the

Re: dialog=1 for window.open from content

2015-10-01 Thread Justin Dolske
On 10/1/15 1:34 PM, Mike Conley wrote: I'm currently working on bug 1095236 - that's an e10s bug for us failing to open any windows if the features string includes dialog=1 (or dialog=yes). According to [1], setting dialog=1 makes a popup window that removes the min/max/restore buttons, and no

Re: dialog=1 for window.open from content

2015-10-01 Thread Blake Kaplan
Mike Conley wrote: > Are there any really good arguments to keep supporting it? I don't know how much data we have for dialog=1, but we'll end up needing to be able to do this for for showModalDialog (see bug 981796 and bug 1137025). -- Blake Kaplan

Content sniffing: seeking reliable protection of a text HTTP resource

2015-10-01 Thread Incnis Mrsi
Hello. This message asks for opinions and suggestions how to make Mozilla products understand «Content-Type» of a Web resource exactly as specified in HTTP(s) headers. Content sniffing in browsers is a compromise between standards and interoperability with “poor” Web sites. It creates

Re: dialog=1 for window.open from content

2015-10-01 Thread Ehsan Akhgari
On 2015-10-01 4:34 PM, Mike Conley wrote: Hello dev-platform, I'm currently working on bug 1095236 - that's an e10s bug for us failing to open any windows if the features string includes dialog=1 (or dialog=yes). According to [1], setting dialog=1 makes a popup window that removes the

Building js/xul/css from Firefox faster

2015-10-01 Thread Mike Hommey
Hi, I recently landed a new build backend that, if you opt-in to running it, will make your non-C++ changes to Firefox more readily available in local builds. After you built Firefox normally once, and assuming you only changed non-C++ code, you can now use the following command for a faster

Disabling C++ tests by default?

2015-10-01 Thread Gregory Szorc
Currently, the Firefox build system builds C++ tests by default. This adds extra time to builds for something that a significant chunk of developers don't care about because they don't run them. An easy way to get faster builds is to disable C++ tests by default (requiring a mozconfig entry to

Re: Disabling C++ tests by default?

2015-10-01 Thread Kyle Huey
How much time does it save? - Kyle On Thu, Oct 1, 2015 at 10:10 PM, Gregory Szorc wrote: > Currently, the Firefox build system builds C++ tests by default. This adds > extra time to builds for something that a significant chunk of developers > don't care about because they

Re: Disabling C++ tests by default?

2015-10-01 Thread Mike Hommey
On Thu, Oct 01, 2015 at 10:10:39PM -0700, Gregory Szorc wrote: > Currently, the Firefox build system builds C++ tests by default. This adds > extra time to builds for something that a significant chunk of developers > don't care about because they don't run them. > > An easy way to get faster