No bug: Remove "unsigned comparison" warning in ScriptSource::setIntroducedFilename. rs=waldo
Back out ed6e04e6fc0c (bug 968642) for breaking Windows plugin tests
CLOSED TREE
bug 934760 - implement synthetic APK update flow; r=wesj
Bug 967589 - Add OOM test for runtime creation and fix failures r=billm
Bug 457296 - allow content manager to removing mail address permissions. r=josh
Bug 964421 - Add a mechanism to HandleLongTap(Up) to allow content to preventDefault touches and stop panning while long tapping. r=kats
Bug 964421 - Fix APZC gtest to simulate some TabChild behavior. r=kats
Bug 969022 - remove s*_ids static constructors by explicitly tracking id initialization state; r=bz
Bug 957332 - setting caret offset doesn't always clear visual selection, r=tbsaunde
Second debugging patch for bug 968200
Bug 844784: Update NSPR to NSPR_4_10_4_BETA3. Also includes the fix for
bug 939786.
Bug 964200 (Part 3a moz2d) - Implement Filter Effects Module feDropShadow filter. r=mstange

--HG--
rename : content/svg/content/src/SVGFEGaussianBlurElement.cpp => content/svg/content/src/SVGFEDropShadowElement.cpp
rename : content/svg/content/src/SVGFEGaussianBlurElement.h => content/svg/content/src/SVGFEDropShadowElement.h
rename : dom/webidl/SVGFEGaussianBlurElement.webidl => dom/webidl/SVGFEDropShadowElement.webidl
Bug 969866 - Use fallible allocations in some places in our font/text shaping code; r=jfkthame

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Bug 969871 - Use fallible allocation for text hyphenation; r=jfkthame

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Bug 959768 - Add non-unified mozconfigs for desktop and mobile builds; r=catlee
Bug 968631 - Port some LOCAL_INCLUDES variables to moz.build
Bug 969757 - Remove support for OS/2
Bug 969865 - Fix the allocation handling of frame time recording

FramesTimingRecording::mIntervals should use fallible allocations, as
the code which is using it is prepared to handle OOM conditions.
However, this handling is not required for the array argument passed to
LayerManager::StopFrameTimeRecording, since that array is coming from
the IPDL protocol, and as of bug 967167 we handle the OOM conditions at
the IPDL protocol layer properly, so no extra OOM handling is necessary
here.

https://bugzilla.mozilla.org/show_bug.cgi?id=969865
Use fallible allocations in some places in our plugin code

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.
Use fallible allocation in WebGL element array cache; r=bjacob

It seems like the sizes for these data structures can be controlled from
Web content, and we are already prepared to deal with OOM conditions,
except that we are using infallible allocations by mistake.