Intent to implement: CSS Font Loading API

Summary: The CSS Font Loading API provides a mechanism for authors to load a font from the network that can then be used from the font-family property. This allows control over when the font load happens -- something that fonts referenced by @font-face rules currently occurs only when a glyph

Re: Proposal for adding named arguments to C++

On 06/15/2014 05:04 AM, Botond Ballo wrote: > I would love to get more people at Mozilla involved in C++ > standardization / get more organized about it. > > I also have a standing offer to assist anyone at Mozilla who would > like to write a standards proposal do so, and present the proposal > at

Re: LeakSanitizer is now enabled for Mochitests

On Sat, Jun 21, 2014 at 6:30 AM, Andrew McCreight wrote: > I just enabled LeakSanitizer (LSan) for ASan Mochitest runs on inbound, in > bug 988041. Woohoo! This is great news. Here are some of the larger leaks that Andrew told me about: > * Bug 1000548 - The new PKIX library was (I think) call

LeakSanitizer is now enabled for Mochitests

I just enabled LeakSanitizer (LSan) for ASan Mochitest runs on inbound, in bug 988041. LeakSanitizer is a special mode of AddressSanitizer that detects when allocations are not freed by shutdown, and reports the allocation stack for any such leaked blocks. We already have good coverage in debug

BzAPI Compatibility API has been rolled out to production BMO

Until recently, Bugzilla supported only older Web technologies, namely XMLRPC and JSONRPC. The BMO team created a new REST API in the summer of 2013 to provide a modern Web interface to Bugzilla. Prior to the native REST API[1], a separate proxy service called BzAPI[2] was created that provi

Re: Code coverage [was: Re: Javascript code coverage ?]

On 6/20/14, 5:00 AM, Joshua Cranmer 🐧 wrote: On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: It takes around 26 hours on my workstation to run all the tests and about 4 days on (old?) Macbook pro. I haven't work on improving this yet. I am mildly distrustful of results that aren't running on as c

Re: C++ standards proposals of potential interest, and upcoming committee meeting

On Tue, Jun 10, 2014 at 3:31 AM, Botond Ballo wrote: > > Reflection proposals (these are very early-stage proposals, but they > give an idea of the directions people are exploring): > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3987.pdf > http://www.open-std.org/jtc1/sc22/wg21/doc

Re: Guidelines for naming preferences?

On 6/19/2014 10:00 PM, Masayuki Nakano wrote: I'm looking for guidelines for naming preferences. However, I've never found it yet. I guess that there is no guidelines. That is correct. The current rule is to use common sense and coordinate with the module owner. If the pref will be exposed

Re: Code coverage [was: Re: Javascript code coverage ?]

On 6/20/14, 8:00 AM, Joshua Cranmer 🐧 wrote: (there is 0% coverage of angle). That's not surprising given that the code coverage test is being done on Linux, is it? -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.

Re: Code coverage [was: Re: Javascript code coverage ?]

On 20/06/2014 14:00, Joshua Cranmer 🐧 wrote: > On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: >> It takes around 26 hours on my workstation to run all the tests >> and about 4 days on (old?) Macbook pro. >> I haven't work on improving this yet. > > I am mildly distrustful of results that aren't runn

Re: PSA: Refcounted classes should have a non-public destructor & should be MOZ_FINAL where possible

Here's an update on this front. In Bug 1027251 we added a static_assert as discussed in this thread, which discovered all remaining instances, and we fixed the easy ones, which were the majority. The harder ones have been temporarily whitelis

Re: C++ standards proposals of potential interest, and upcoming committee meeting

On 6/20/2014 4:44 AM, Botond Ballo wrote: Why object to this proposal, then? Even if it will, in practice, take a very long time for some projects to adopt extern "abi" and std::abi, this seems better than the status quo. Is the status quo really that bad? MSVC can publish its ABI as is, and w

Re: Code coverage [was: Re: Javascript code coverage ?]

On 6/20/2014 4:25 AM, Sylvestre Ledru wrote: It takes around 26 hours on my workstation to run all the tests and about 4 days on (old?) Macbook pro. I haven't work on improving this yet. I am mildly distrustful of results that aren't running on as close to the same configuration as our builder

Re: C++ standards proposals of potential interest, and upcoming committee meeting

- Original Message - > From: "Joshua Cranmer 🐧" > > On 6/19/2014 5:55 PM, Botond Ballo wrote: > > Are you saying that gcc - assuming that for some platforms, it is > > considered the platform vendor, and therefore the provider of std::abi - > > would likely ship their non-conforming std::

Code coverage [was: Re: Javascript code coverage ?]

Hello, Thanks for the various answers. On 17/06/2014 00:53, Clint Talbert wrote: > Inline > On 6/16/2014 10:23, Sylvestre Ledru wrote: >> Hello, >> >> I am working on providing weekly code coverage of Firefox code. >> For now, I am able to do that for C/C++ code. > Awesome. Where are you putt

Re: Is it time for mochitest-chrome on Android and B2G

Yeah, this caught me out yesterday. xpcshell tests on Android have, for instance, a pre-existing default search engine, whereas xpcshell tests running on desktop do not. It would be nice if this were documented on MDN. ~ Gijs On 20/06/2014 02:24, Mark Finkle wrote: Fennec/Android does have t