Bug 888787 - Restore old XBL behavior when a child of the bound element didn't match any of the <children/> in the binding. r=sicking
Bug 888787 - Add reftests. r=sicking
Bug 889911 - Introduce xpc::SystemErrorReporter, roughly based on mozJSComponentLoader's error reporter. r=mrbkap
Bug 889911 - Replace mozJSLoaderErrorReporter with SystemErrorReporter and remove the former. r=mrbkap
Bug 889911 - Fix tests that unconditionally throw for things reported to the console. r=mrbkap

When we start sending everything reported to the JSErrorReporter to the console,
these tests end up getting confused by warnings.
Bug 889911 - Switch xpcshell to SystemErrorReporter with a little bit of special magic. r=mrbkap

XPCShell currently overrides all the JSContexts whose creation it observes with
its own custom error reporter. This reporter does all sorts of funny things which
we try to clean up for the most part. But there are a few very intricate
considerations at play.

First, the old xpcshell error reporter does some mumbo jumbo with the
XPCCallContext stack to try to guess whether some other code might catch the
exception. This is total garbage on a number of fronts, particularly because
the XPCCallContext stack has no concept of saved frame chains, nested event
loops, sandbox boundaries, origin boundaries, or any of the myriad of
complicating factors that determine whether or not an exception will propagate.

So we get rid of it. But this causes some crazy debugger tests to fail, because
they rely on an exception from uriloader/exthandler/nsHandlerService.js getting
squelched, and can't handle anybody reporting errors to the console service at
the particular moment of contortionism when the exception is raised. So we need
to introduce an explicit mechanism to disable the error reporter here to keep
things running.

Second, we have to be very careful about tracking the return status of the
xpcshell binary. The old code would simply flag an error code if the error
handler was invoked, and we can mostly continue to do that. But there are some
complications. See the comments.

Finally, we don't anything analogous in XPCShellEnvironment, because I have
patches in bug 889714 to remove its state-dependence on the error reporter.
I'll switch it to SystemErrorReporter in that bug.
Bug 892287 - Add re-entrancy guards to store buffer mark/put; r=billm

--HG--
extra : rebase_source : 14396f2bebeb8794c7b22a0eadff9de0a471b31d
Bug 892287 - Simplify post barriering of TypedArray's internal pointers; r=sfink

--HG--
extra : rebase_source : ce417f347a577c559847f28aa2ca84d7cb7c2bc1