Bug 451771 - disabling input greys background. r=jimm
Bug 792989 - Added ErrorNames.h and ErrorNames.cpp. r=nfroyd
Bug 792989 - Updated Dashboard.cpp to use ErrorNames. r=nfroyd
Bug 1020172 - Patch 1: Replace process id with ContentParentId type - v3. r=khuey
Bug 1020172 - Patch 2: Manage TabParent in chrome process - v14. r=khuey
Bug 1020172 - Patch 3: Use TabId to replace uint64_t of PBrowserOrId - v2. r=khuey
Bug 1020172 - Patch 4: Replace ManagedPBrowserParent in AppProcessChecker - v2. r=khuey
Bug 1079385 - Send NS_NETWORK_LINK_DATA_CHANGED event on Mac OS X. r=joshmoz
Bug 1081926 - Fallback on a simple image lookup when the normal lookup fails. r=mattwoodrow
Bug 1082098 - Part 1 - Return correct change hint when scroll-behavior CSS value changes. r=roc
- When the scroll-behavior CSS value changed, the nsChangeHint_NeutralChange
  hint was returned by nsStyleDisplay::CalcDifference.  It now returns
  nsChangeHint_ReconstructFrame to ensure that the change takes effect.
- When scroll-behavior is changed, the nsChangeHint_NeutralChange was not
  sufficient to enter nsCSSFrameConstructor::PropagateScrollToViewport.  By
  using the same hint as used when the overflow css property changes,
  nsChangeHint_ReconstructFrame, PropagateScrollToViewport will be called.
- The scroll-behavior css property is not expected to change often (the
  CSSOM-View DOM methods are likely to be used in those cases); however, if
  this does become common perhaps a faster-path might be worth while.
Bug 1082098 - Part 2 - Tests. r=roc
- scroll-behavior-8.html - Tests if dynamically changing the scroll-behavior
  css property on a div element takes effect after the page has been painted and
  reflowed.
- scroll-behavior-9.html - Tests if dynamically changing the scroll-behavior
  on the body element takes effect after the page has been painted and
  reflowed.
Bug 1088950 - Fix handling of inappropriate_fallback alert. r=keeler
Bug 1088950 - Adding some testing. r=dkeeler
Bug 1089305 - Switch EV tests to SQL DB and partially clean up scripts. r=keeler
Bug 1089619 - Stop abusing the Settings API from Gonk GPS. r=kanru

GPS handling for Gonk abuses the Settings API in two ways. First, on
mozsettings-changed event, it will trigger two new requests to read
values (debug enabled and GPS locations ignore). This is useless since
the event already contains the key that has changed and the new value,
so there is no need to do a createLock().get() call. Then, in startup
code, the Init() method is supposed to check itself whether it is
already running. This is done through the mStarted boolean. The same
Init() method is responsible for adding the mozsettings-changed
observer, which is removed by the Shutdown() method. Investigation on
device by using the Geolocation API has proven that we were leaking some
observers. This is because checking mStarted boolean is performed after
we request settings values and we install the mozsettings-changed
observer. So any time the Init() gets called, we install it but we just
remove it once in Shutdown().
Bug 1090785 - Migrate to NSPR logging for touch caret. r=roc
Bug 1090869 - Don't collect output glyphs when checking for features involving <space>. r=jdaggett
Bug 1090906, no context menu when pointer is locked, r=masayuki
Backed out changeset 6797040a2034 (bug 1089619) for breaking non-unified b2g builds
Backed out changeset 83f801de85fb (bug 792989)