Bug 1403348 - Include details about AsyncShutdown failure in crash reason. r=baku, data-r=rweiss, a=ritu MozReview-Commit-ID: L6U2MVshZl8

Bug 1405166 - Update occurrences of system-disabled pref outside screenshots system addon. r=kmag, a=ritu MozReview-Commit-ID: 24PV53VM6te

Bug 1405166 - Remove system-disabled pref from Screenshots. r=kmag, a=ritu MozReview-Commit-ID: KuDfW6EZMWZ

Bug 1404495 - Back out changeset 3e7cd55f6cb9 to go back to different colors for connecting and loading on unselected tabs. r=Gijs, a=ritu MozReview-Commit-ID: JTVjsavmob6

Bug 1403728 - Remove unwanted padding. r=jwu, a=ritu MozReview-Commit-ID: lMO3l83226

Bug 1403132 - Orange color when tapping Get started button. r=jwu, a=ritu MozReview-Commit-ID: BffcsiT1wrF

Bug 1351190 - Revert the change we made in this bug, since it causes a crash in bug 1404681. r=me, a=ritu MozReview-Commit-ID: 87CBqK6upIU

no bug - Bumping Firefox l10n changesets DONTBUILD r=release a=l10n-bump cs -> 91049dcc2917 da -> 8562978358c2 gu-IN -> 9509b16b3d75 pt-PT -> d56af02bfb40 tr -> a69aa228c1cc zh-CN -> 40be4448de31

no bug - Bumping Fennec l10n changesets DONTBUILD r=release a=l10n-bump cs -> 91049dcc2917 da -> 8562978358c2 ja -> f6cc8ebec818 pt-BR -> 8825c351b391

Bug 1369778 - Reset search expiration on major updates. r=florian, a=ritu MozReview-Commit-ID: Jcr2dx9Bbza

Bug 1403402 - Should not migrate profile for a fresh install. r=MattN, a=ritu MozReview-Commit-ID: D9uMUXO2PV5

Bug 1348981 - Only load system add-ons from a built-in list. r=kmag, a=ritu MozReview-Commit-ID: A6c5kaLmNPP

Bug 1348981 - Provide method to re-initialize URLPreloader for xpcshell tests. r=kmag, a=ritu MozReview-Commit-ID: rnjEJc1Uir

Bug 1348981 - Add Cu.readURI helper for sync file reading on startup. r=kmag, a=ritu MozReview-Commit-ID: 1yz25afCUDs

Bug 1348981 - Provide a list of valid system add-ons for packaging. r=glandium, a=ritu MozReview-Commit-ID: K2jCHBBJBqw

Bug 1343147 - Part 2. A crash test of painting elements with both perspective and transform in generate text mask for background-clip:text. r=mstange, a=ritu MozReview-Commit-ID: 6KKo9ap2VZu

Bug 1343147 - Part 1. Do not double applying transform vector of the root frame in a glyph mask into the target context. r=mstange, a=ritu When we generate the glyph mask for a transformed frame in GenerateAndPushTextMask, the transform vector had been applied into aContext[1], so we should find a way to prevent applying the vector again when painting the glyph mask. In bug 1299715, I tried to prevent double apply at [2], it caused two problems: 1. We only skip generating nsDisplayTransform, but we may still create a nsDisplayPerspactive bellow. Since the parent of a nsDisplayPerspective must be a nsDisplayTransform, which have been ignored, so we hit this assertion. 2. We skip all transform for all frames while painting the glyph mask, which is not correct. We should only skip double applying transform vector of the root frame. This patch fixes both of these issues: a. We will still create a nsDisplayTransform for the root frame if need. But the transform matrix we apply into the target context will be an identity matrix, so we fix #1 above. b. In #a, we change the transform matrix to an identity matrix only for the root frame of the glyph mask, so we fix #2. [1] https://hg.mozilla.org/mozilla-central/file/59e5ec5729db/layout/painting/nsDisplayList.cpp#l752 [2] https://hg.mozilla.org/mozilla-central/file/ce2c129f0a87/layout/generic/nsFrame.cpp#l2806 MozReview-Commit-ID: 973lkQQxLB6

Bug 1404206 - Part 3: Make GeckoInputConnection handle "mozAwesomebar" inputmode value as "url". r=jchen, r=gijs, a=ritu Although, Firefox for Android doesn't use urlbarBindings.xml for declaring its awesome bar, for consistency with widget code for desktop OSes, GeckoInputConnection should treat "mozAwesomebar" inputmode value as "url" since Android doesn't have any special input type for "search" and we should keep current behavior. MozReview-Commit-ID: DpUnUx4E2Sp

Bug 1404206 - Part 2: Make TSFTextStore and IMEHandler handle "mozAwesomebar" inputmode value. r=m_kato, r=gijs, a=ritu When "mozAwesomebar" is set to inputmode value, that means that the Smart Location Bar gets focus. In that case, we should notify IME of input scopes as "URL" because on-screen keyboard for URL has some useful additional keys but they are not hindrances even when users want to type non-URL text. On the other hand, MS-IME for Japanese and Google Japanese Input changes their open state to "closed" if we notify them of URL input scope. A lot of users complain about this behavior. Therefore, we should notify only them of "Default" input scope even when "mozAwesomebar" has focus. MozReview-Commit-ID: DIgqpR7TXQx

Bug 1404206 - Part 1: Smart Location Bar should have special inputmode value, mozAwesomebar. r=smaug, r=gijs, a=ritu Smart Location Bar (a.k.a URL bar) has some features, loading inputted URL directly, searching bookmark items and history items, and search inputted words with registered search engine. So, it does not make sense its inputmode is "url". E.g., neither showing URL specific software keyboard nor switching IME open state automatically for typing URL may not be expected in most cases. Unfortunately, there is no proper inputmode value for Smart Location Bar. Therefore, this patch uses "mozAwesomebar" value and accepts the value only in chrome documents. This value should be handled by each native IME handler properly. MozReview-Commit-ID: 7vUnbpg91F2