Bug 905454 - Fix delete key in e10s (r=felipe)
Bug 899222 - Make about:home work via message passing (r=felipe).

--HG--
rename : browser/modules/AboutHomeUtils.jsm => browser/modules/AboutHome.jsm
Bug 888898 - Fix rooting in setObjectMetadataCallback (r=bhackett)
Backout bug 899222 (forgot to apply review comments)

--HG--
rename : browser/modules/AboutHome.jsm => browser/modules/AboutHomeUtils.jsm
Bug 905002: backout bug 879717 until we can fix the mac-only regression rs=roc
Bug 863306: Propagate RTCP_MUX Status to pipeline via VCM. r=abr
Bug 905215 - Add a test sheet for HTML elements, r=davidb
Bug 865253 - Part 1: Implement the DOM bindings for OscillatorNode; r=roc
Bug 865253 - Part 2: Implement the alternate enum values for OscillatorNode; r=roc
Bug 865253 - Part 3: Direct generation of fixed oscillator types. r=ehsan

Simple direct calculation of the fixed types.

We probably want to use the PeriodicWave machinery to generate
the pre-defined waveforms once it's available. In either case
we can optimize this significantly by caching the generated
waveform when the frequency is stationary over the block.
Bug 865253 - Part 4: Stop OscillatorNodes on context shutdown. r=ehsan

Like AudioBufferSourceNode and ScriptProcessorNode, OscillatorNode
holds a self-reference in mPlaying. Keep track of all osc nodes
in the AudioContext and explicitly stop them to make sure this
reference is dropped.
Bug 865253 - Part 5: Shorten a comment to fit in 80 columns. r=ehsan
Bug 905437: Make it possible for 'mach xpcshell-test' to run xpcshell under GDB. r=ted

At the moment, the --debug argument accepted by mach xpcshell-test is
dropped. I don't know if just bringing the old harness's command-line
arguments forward to 'mach xpcshell-test' is the most mach-ish way to do
things, but it does let me get things started.
Bug 858622 - Make jit-tests runnable on mobile;r=terrence
Bug 901106 - Deserialize FastLoad scripts into the compilation scope, rather than the scope of the first document created. r=smaug

This code dates back to 2003, and smaug and I both think it's probably a bug.
In fact, it might cause leaks, because the prototype document would hold the
script alive, the script would hold the document alive, and the document would
hold the prototype document alive in the cache.
Bug 901106 - Inline and remove nsIScriptContext::{Serialize,Deserialize}. r=smaug
Bug 901106 - Be more direct in nsXULPrototypeScript::Compile. r=smaug

Given that this is just the phony compilation global we're dealing with, the
only thing relevant about this script context is that it defaults to the right
compartment. But we can do that manually with the SafeJSContext.

The CanExecuteScripts check was something I added to address review comments
in bug 901162 comment 8. I now realize that it's effectively a no-op, because
the nsIScriptContext here corresponds to the compilation scope, not the
document, so it will never have script disabled.
Bug 901106 - Pass nsXULPrototypeDocuments directly through serialization and use AutoSafeJSContext at the serialization point. r=smaug
Bug 901106 - Stop implementing nsIScriptGlobalObjectOwner in nsXULPrototypeDocument. r=smaug
Bug 901106 - Stop using nsIScriptContext for XUL prototype documents. r=smaug

This patch is roughly analagous to what I did for XBL compilation scopes in
https://hg.mozilla.org/mozilla-central/rev/26898c90f9cc.

According to CC dumps, the gray unmarking during MarkInCCGeneration prevents this
stuff from being traversed during CC.