Bug 1083071 - Avoid touching D3D11 at all, even to test if it works, if D3D11 layers are blacklisted. r=Bas, r=jmuizelaar
Bug 1080302 (part 1) - Add support for --foo and /foo options where it's not already present. r=glandium.
Bug 1080302 (part 2) - Convert all mentions of -foo options to --foo options in comments, help messages and error messages. r=glandium.
Bug 1080302 (part 3) - Convert -foo options to --foo in |mach run|. r=glandium.
Bug 1087824 - Bump the limits some more. r=luke
No bug - Remove the executable bit from HTMLMediaElement.{h,cpp}.
Bug 1086510 - Remove set-only flags from HTMLContentSink; r=hsivonen
Bug 1089370 - Don't null-check a reference in nsContentUtils::CreateContextualFragment; r=jst
This triggers an undefined-bool-conversion warning in recent LLVM. The
dereference is safe because nsAutoTArray is infallible.
Bug 1082178 - JS initialization must happen using the correct preferences in workers, r=khuey
Bug 886390 part 1 - Implement behavior equivalent to the adjusted current node concept by changing the first node on the stack. r=wchen.
Bug 886390 part 2 - Disable foreign content breakout in the fragment case. r=wchen.
Bug 886390 part 3 - Import html5lib tests for fragment parsing with a foreign context node. r=jgraham.
Bug 886390 part - Adjust namespace expectations for SVG and MathML on a previous innerHTML test. r=wchen.
Bug 1084997 - Replace '\' in MOZ_BUILD_APP with '/' to eliminate the difference between windows and others. r=glandium
Bug 1082001 - Cleanup settings lock from parent itself. r=bent

From bug 1065128 SettingsManager has been changed to listen the
dom-window-destroyed event for its cleanup. However, when running Gaia
in Mulet, a race condition is exposed. For B2G, when loading a page,
about:blank is first used. This means that window destroyed events will
be triggered. However, from the dom-window-destroyed event we cannot
distinguish whether this is about:blank or a legit application being
closed. SettingsManager gets initialized (i.e., init() called) when the
application makes use of navigator.mozSettings. So the chain of event is
that we have a SettingsManager living because System app did some
request. At this time, about:blank is being unloaded and triggers a
dom-window-destroyed event. This makes SettingsManager doing its
cleanup, especially freeing the window reference. Then in the meantime,
we have the navigator.mozSettings use that is progressing. At some
point, SettingsManager has no more window to send messages to, and Gaia
is not able to even start.

SettingsRequestManager lives on the parent process and SettingsManager
lives on the child side. Part of the cleanup performed by
SettingsManager was to ensure pending locks on the parent process would
be forced to finalize to make sure those are being properly committed.
We move this cleanup to SettingsRequestManager and we augment the lock
informations with the proper inner window id. This way we can track
which lock is attached to which inner window when the lock gets created.
And thus we can listen on inner-window-destroyed from
SettingsRequestManager to be able to force finalize on any pending lock.
Impacted code path are those were we are not running out of process.
When we are running out of process, SettingsRequestManager already
listens on the child-process-shutdown event to perform the lock
finalization.
Bug 1083449 - Use a shared mutex instead of a per-instance mutex to protect ifc commands. r=vchang, r=chucklee
Bug 1087152 - Ignore the failure cause by ifc_remove_route "0.0.0.0" or "::". r=vchang
Bug 1085330 - UITour: Highlight positioning breaks when icon target moves into "more tools" overflow panel. r=Unfocused
Bug 1078718 - Force standalone app reload on hashchange event. r=Standard8
Bug 1053434 - CSS changes for DevEdition on Linux. r=Gijs