Bug 1328868 - Part 11 - Check that zooming via "font.size.systemFontScale" actually has any effect. r?sebastian MozReview-Commit-ID: F2YtTER17xQ

Bug 1328868 - Part 10 - Add a test to check that flipping the Android pref enables/disables font inflation. r?esawin,sebastian A basic check that the listener is indeed operational. MozReview-Commit-ID: 6KijcsRaScI

Bug 1328868 - Part 9 - Move MakeObserver() into head.js r?esawin We can use this function for our upcoming test as well, so we should move it into the common header. MozReview-Commit-ID: H5ANDAlnpmm

Bug 1328868 - Part 8 - Detect the previous font size setting and migrate it to the new shared preference. r?sebastian If the shared preference doesn't exist on startup, we check the value of font.size.inflation.minTwips and then turn the new setting on if minTwips was > 60, which is the case if the previous font size setting was set to at least "Small" or larger. If the old setting was "Tiny" or else for new installations, we default the new setting to "off". MozReview-Commit-ID: B9yB9JwRcqj

Bug 1328868 - Part 7 - Remove the old font size preference and its associated code and resources. r?sebastian MozReview-Commit-ID: EgL3WFo6mdo

Bug 1328868 - Part 6 - Add a Java-side listener watching the new pref and the Android system font scale. r?sebastian The state of the switch added in Part 5 is stored in our Android-side shared preferences. For this to have any actual effect on rendering, we now add a class that is initialised when Gecko starts up and listens to changes of that particular pref. When it is turned on, we enable font inflation and add another listener for the system font scale, which then forwards the current font scale as well as any changes to Gecko, so mobile mode pages can be scaled correspondingly as well. When the setting is turned back off again, the system font scale listener is stopped again and the Gecko font size settings reverted back to their default values. MozReview-Commit-ID: GyffpZTQQX8

Bug 1328868 - Part 5 - Add a new switch offering to honour the system font size to Fennec's preferences. r?sebastian,antlam MozReview-Commit-ID: HZqxl6T90mZ

Bug 1328868 - Part 4 - Don't zoom Contentviewer children when setting the zoom from the PresShell. r?tnikkel Normally, setting the zoom via the ContentViewer will also set the zoom of all the ContentViewer's children. Here however this is not necessary, since each PresShell is already running the code to set the zoom according to the system font scale and will therefore call its ContentViewer's zoom function on its own. Alternatively, we could simply bypass the ContentViewer and set the zoom directly on the PresContext, however doing it the way we are doing it now means that the ContentViewer will be able to report the actual text zoom factor that has been applied if anybody queries it, which we'll make use of later in testing. MozReview-Commit-ID: 7nk5EDNY2FZ

Bug 1328868 - Part 3 - Copy the global zoom state over into new presShell when navigating/reloading. r?tnikkel When the global zoom factor is set to 1.0f, i.e. when this feature has been turned back off or simply was never enabled, we want to be able to return early and not set any zoom factor. To that effect, we need to call setTextZoom(1.0f) once when going from systemFontScale != 0.0f to systemFontScale == 1.0f in order to reset the text zoom to its default value. We do this by keeping track of the global zoom state of each PresShell via mGlobalZoomWasEnabled, however for this to properly work, we need to copy this bit of state over into any new presShell that gets created when reloading the document or navigating back-/forward (with or without the bfcache) . MozReview-Commit-ID: AqNOGIMsRt

Bug 1328868 - Part 2 - When font.size.systemFontScale is enabled, apply a global zoom factor to all pages that are not font inflated. r?tnikkel We want to use a similar model as Chrome on Android does for scaling our display of web content, that is use font inflation for desktop pages and plain text zooming for everything else. As long as font inflation is enabled in principle (e.g. font.size.inflation.minTwips != 0), every page starts out as eligible for font inflation until the relevant meta viewport tags marking the page as "mobile friendly" have been detected. Since the PresShell caches the font inflation state and only recalculates it when necessary, we make use of that and turn our text zoom on or off as necessary whenever the font inflation state has been refreshed. MozReview-Commit-ID: 2InyE04wKAW

Bug 1328868 - Part 1 - Allow setting a global zoom factor via nsLayoutUtils. r?tnikkel,billm For Android we want to be able to set a global zoom factor that will scale any page where font inflation is not turned on. Android makes the system font scale available as a float factor. For our purposes, converting this to a percentage based value and rounding to an integer is accurate enough and enables us to pass this value as a standard Gecko int preference. This means we can make use of the standard infrastructure for setting and retrieving Gecko-side preferences both from Java and JS (the latter during testing), as opposed to having to write custom JNI and C++/IDL helper functions. To that effect, we implement a method for retrieving that setting via nsLayoutUtils, analogous to the current font inflation settings. Unlike those, we use a custom preferences listener though, since we want to clamp the font scale factor between the limits of zoom.minPercent and maxPercent as a sanity limit. Because we're mimicking the existing font inflation prefs, we also need to add this new pref to the bug 1303096 whitelist. MozReview-Commit-ID: Ler2YmwzImE

Bug 1328868 - Part 0 - Remove unneeded imports. r?esawin MozReview-Commit-ID: 5mCrZ8aOAiw

Local Gradle tweaks MozReview-Commit-ID: H5pdKja8p2a

Bug 1338525 - Add schema validation for webextension themes r?mikedeboer MozReview-Commit-ID: 3QjDrTeMKH0

Bug 1337825 - Jamun: Change android-api-15-{l10n,nightly} to l10n bumped file r=aki Also adds missing files MozReview-Commit-ID: C0G6bE6wmK4

Bug 1339673 - Don't link the gtest libxul during MOZ_PROFILE_GENERATE. r=ted The gtest libxul isn't used during the profiling run, so this is just wasted work. MozReview-Commit-ID: 5FVmt8rA4zk

Bug 1340022 - Implement "handled for descendants" tracking for RestyleDamage. r=emilio MozReview-Commit-ID: Bbk99ogILXC

Bug 1331322 - Tweak some fuzzy annotations. r=heycam MozReview-Commit-ID: ERcDYiwUaS7

Bug 1333270 - wait until we find a word before we yield/ await the toggle highlight promise to avoid timing issues when switching to a remote browser element. r?jaws MozReview-Commit-ID: F0kq7oYm8WS

Bug 1339575 - Allow nsDisplaySolidColor to be forced active. r?mstange MozReview-Commit-ID: AxxzuRQF8vT