Bug 1092191 - Do not warn about failure to load _Z35eglQueryStringImplementationANDROIDPvi. r=dglastonbury
Bug 1092477 - Let the subscript Loader report any URL it fails on, when it can.  r=bholley
Bug 1094056 - Use nsCaret::GetGeometryForFrame to determine position of selection carets. r=roc
Bug 1094519 - Advertise h2-15 in addition to h2-14. r=mcmanus
Bug 1094525 - Simplify touch resampling code in GeckoTouchDispatcher, r=kats
Bug 1094913 - Test for detecting attribute 'pointerType' in got/lostpointercapture events. r=smaug
Bug 1094913 - Set pointerType to got/lostpointercapture events. r=smaug
Bug 1093573 part 9 - Add InterpretGeneratorResume. r=wingo
Bug 1093573 part 10 - Baseline-compile JSOP_RESUME. r=shu,wingo
Bug 1093573 part 11 - Remove bytecode offset slot from generators. r=wingo
Bug 1096487 - part 1 - make ipdl message constructors set their priority directly; r=bent

The default constructor for ipdl-generated messages looks like:

    MOZ_IMPLICIT Msg_AsyncMessage() :
        IPC::Message(MSG_ROUTING_NONE, ID, IPC::Message::PRIORITY_NORMAL, COMPRESSION_NONE, "PContent::Msg_AsyncMessage")
    {
    }

IPC::Message::PRIORITY_NORMAL is 1, so any set_priority(1) calls are
just redudant.

Additionally, the priorities for messages are known at code generation
time, so we are always able to provide the right constants to the
message constructor, rather than using set_priority calls later.
Bug 1096487 - part 2 - make ipdl message constructors take their routing id; r=bent

Similarly to part, there's no need to say we don't know the routing id
when constructing a message, and then turn around and set the routing id
immediately afterwards.  Just let the constructor do its work.
Bug 1095751 - Pass optional device serial to mozversion in Marionette runner. r=ahalberstadt
Bug 1090929 - Enable the conditional breakpoint tests;r=mratcliffe
Bug 1090929 - Enable the parser tests;r=mratcliffe
Bug 1038868 - Use B2GDeviceRunner in the Marionette client. r=ahalberstadt
Bug 1071205 - Change Video encode to HardwareCodecsOnly r=mikeh
Bug 1097293: Do not draw radial gradients when centers and radii are identical. r=jrmuizel

When Cinner and Couter are equal, as well as Rinner and Router, the algorithm described in the canvas specification will hit a division by 0. As described in section 7 of the Canvas2D specification nothing should be drawn in this situation.
Bug 1097476: Fix typo in D2D 1.1 radial gradient code. r=jrmuizel
Bug 1097628: Mark tests as fuzzy with D2D even when Canvas & Content backends are identical. r=jwatt