Re: W3C Proposed Recommendation: longdesc

On Wed, Jan 7, 2015 at 1:13 AM, L. David Baron wrote: > W3C recently published the following proposed recommendation (the > stage before W3C's final stage, Recommendation): > > http://www.w3.org/TR/html-longdesc/ > HTML5 Image Description Extension (longdesc) > > There's a call for review to W

Memory management in C programs

"" One large difference between C and most other programming languages is that in C, you have to handle memory yourself rather than having a garbage collector do it for you. Ensuring that memory is allocated at the correct moment is not very difficult (and something that needs to be done manually i

Re: Audio output device selector

What about if I create a firefox plugin? With a C++ plugin can I change the output audio device? Best regards, Balázs SÁNDOR Software Developer Virtual Call Center MUNICH | BUDAPEST | WARSAW

Test Informant Report - Week ending Jan 09

Test Informant report for 2015-01-09. State of test manifests at revision 286e1f883fdb. Using revision 636498d041b5 as a baseline for comparisons. Showing tests enabled or disabled between 2015-01-04 and 2015-01-09. 85% of tests across all suites and configurations are enabled. Summary ---

Re: [blink-dev] Fwd: [Bug 441414] Treerows need a way to hold richer content

On Fri, Jan 9, 2015 at 10:38 AM, Jan Varga wrote: > HTML5 spec used to have something like that called > Here's some info: > https://bugs.webkit.org/show_bug.cgi?id=26545 > > As a former contributor to XUL tree widget, I would love to see a similar > widget in HTML5. > > In general complex widge

Re: Audio output device selector

Our audio output subsystem is not an XPCOM component, so I would say no. Paul. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: How do I use the Dom File API from privileged code (documentation problem)

On 2015-01-11 9:50 PM, Naja Melan wrote: Found some workarounds, see this SO question. MDN updated: https://stackoverflow.com/questions/27893399/how-do-i-use-the-dom-file-api-from-privileged-code/27894221 Thank you for updating the docs! Cheers, Josh _

Good ways to view Firefox compile errors in a terminal?

Hi, If you do |mach build| and get compile errors, often those errors scroll quickly off screen and they are mixed in with other lines of output and it's hard to find them. I deal with this by using a bash alias that calls |mach build| and pipes the output to file. I can then use Vim's quicklists

Re: Good ways to view Firefox compile errors in a terminal?

I use the Konsole terminal, and have the "Find" bar always activated, with "error:" typed in as the search string. When I get a failing build, I click the handy "From bottom" button, which searches backward from the bottom of the terminal output. That takes me to the error I want to see in one cli

Re: Good ways to view Firefox compile errors in a terminal?

|mach warnings-list| and the underlying implementation to parse and store warnings [1] are one of the very first features of mach and there is definite room for improvement. If the functionality isn't doing what you want, send a patch to change it! We probably could integrate warning parsing into

Jemalloc 3 is now on by default

Hi, I just landed bug 762449 on inbound, which enables Jemalloc 3 on the nightly channel. This puts us a step forward to removing mozjemalloc, our highly patched fork of jemalloc 0.9. More importantly, it will allow us to more closely work with upstream, by proposing patches that do apply there (w

Re: Good ways to view Firefox compile errors in a terminal?

On 2015年01月13日 07:28, Gregory Szorc wrote: > |mach warnings-list| and the underlying implementation to parse and store > warnings [1] are one of the very first features of mach and there is > definite room for improvement. If the functionality isn't doing what you > want, send a patch to change it!

Re: Jemalloc 3 is now on by default

On Tue, Jan 13, 2015 at 10:13:34AM +0900, Mike Hommey wrote: > Hi, > > I just landed bug 762449 on inbound, which enables Jemalloc 3 on the > nightly channel. This puts us a step forward to removing mozjemalloc, > our highly patched fork of jemalloc 0.9. More importantly, it will allow > us to mor

Re: Jemalloc 3 is now on by default

On 1/12/2015 9:44 PM, Mike Hommey wrote: Aaand as usual with such changes, it didn't stick. Does that mean I should assume that whenever someone makes this sort of announcement, I should assume they really mean "this will take effect tomorrow or the day after, when I've figured out what went