MozReview-Commit-ID: 9njDcbltyow

--HG--
extra : rebase_source : 774d25f2ac4e4b1a876e48159333188bc722f940

Comment-only, so DONTBUILD (and KWierso says it's OK to land this on CLOSED TREE)

MozReview-Commit-ID: BKxFHeXxipf

Because guest mode is intimately tied to the profile, it'd be hard to
keep guest mode out of geckoview code entirely, But we also don't want
any dependency on GuestSession from geckoview code, so this patch moves
the part of GuestSession that manages guest mode state to GeckoProfile.

Move the first-run telemetry session from GeckoProfile to BrowserApp, so
there is no longer any dependency on Telemetry from inside GeckoProfile.

MozReview-Commit-ID: Cs7xUcPnPoz

MozReview-Commit-ID: 1oVQYPlF89J

--HG--
extra : rebase_source : 365a915d22ee8bd72a3d7ed81fa3a910b96d2387

MozReview-Commit-ID: 8g92o4GXQ82

--HG--
extra : rebase_source : 64dc4699727be013eeb3c9dcca86e519598e1880

Mass convert GeckoProfile.getDB() calls to BrowserDB.from() calls,
whether using Context or GeckoProfile.

Remove references to BrowserDB and its factory from GeckoProfile.
Instead of keeping the DB in mDB, GeckoProfile now keeps an arbitrary
object in mData. Using a data object lets us avoid needing another map
to map profiles to DBs. This feature could be very useful for GeckoView
consumers as well.

The new way to get a BrowserDB from a profile/context is through
BrowserDB.from(Context) or BrowserDB.from(GeckoProfile), which takes
care of creating a local DB if necessary and associating the DB with the
profile.

Remove the input method change notification that GeckoInputConnection
sends to FormAssistPopup, so there's no dependency on FormAssistPopup
from inside GeckoInputConnection or GeckoInterface. Instead,
FormAssistPopup now actively queries the current input method, and
performs blocklisting based on that.

We used to use it to sync viewport metrics between Gecko and Java, but I
don't think this is needed anymore.

The restrictions package really belongs in Fennec code rather than in
geckoview code. The move also eliminates some dependency errors because
the restrictions package references some classes in Fennec code.

--HG--
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/DefaultConfiguration.java => mobile/android/base/java/org/mozilla/gecko/restrictions/DefaultConfiguration.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/GuestProfileConfiguration.java => mobile/android/base/java/org/mozilla/gecko/restrictions/GuestProfileConfiguration.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/Restrictable.java => mobile/android/base/java/org/mozilla/gecko/restrictions/Restrictable.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/RestrictedProfileConfiguration.java => mobile/android/base/java/org/mozilla/gecko/restrictions/RestrictedProfileConfiguration.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/RestrictionCache.java => mobile/android/base/java/org/mozilla/gecko/restrictions/RestrictionCache.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/RestrictionConfiguration.java => mobile/android/base/java/org/mozilla/gecko/restrictions/RestrictionConfiguration.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/RestrictionProvider.java => mobile/android/base/java/org/mozilla/gecko/restrictions/RestrictionProvider.java
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/restrictions/Restrictions.java => mobile/android/base/java/org/mozilla/gecko/restrictions/Restrictions.java

Code in geckoview depends on several string constants in GeckoApp.
This patch moves PREFS_OOM_EXCEPTION and ACTION_ALERT_CALLBACK from
GeckoApp to GeckoAppShell, to reverse the dependency. Ideally, we'd want
those constants to not be used or used differently in geckoview code,
but this is a quick workaround for now. GeckoThread uses
GeckoApp.ACTION_HOMESCREEN_SHORTCUT, but that block of code is actually
obsolete, so this patch removes the code block and the dependency.

This patch includes a small memory optimization of using ArrayList and
`volatile int` for storing the pending thumbnails list and pending
width, instead of using LinkedList and AtomicInteger, respectively.

The patch also fixes a possible race condition due to calling
processNextThumbnail outside of a lock. Now it must be called inside a
lock and its name is changed to reflect that.

Move the "thumbnail:" handler out of BitmapUtils and into
ThumbnailHelper and PromptListItem.

The patch adds two overloads of the getAndProcessThumbnailFor method in
ThumbnailHelper, which handle the tasks of getting a thumbnail for a
specific tab and calling a given BitmapLoader.

Because only PromptListItem makes use of the "thumbnail:" convention,
the actual handling of "thumbnail:" is moved to PromptListItem, which
calls ThumbnailHelper to get the thumbnail.

We no longer send viewport metadata, so we don't actually make use of
the RTL and ZoomConstraints variables we keep in Java. There is a single
usage of an RTL flag in ImmutableViewportMetrics.offsetViewportByAndClamp,
but I think the two branches are equivalent, so the RTL flag is not needed
there either.

Bug 1302275 - Add a way to track Constellations (Units of related similar origin browsing contexts) to nsGlobalWindow, r=billm

MozReview-Commit-ID: AjbVZHEL9WZ

Bug 1296746 - explicitly ignore the result of Send{Observe,Unobserve}Vsync in CompositorWidgetParent; r=jimm

Bug 1298149 - explicitly ignore the result of SendUpdateWindow in ContentParent::SendAsyncUpdate; r=baku

This change doesn't modify the behavior of the code, but it does silence
a clang-cl warning.

Bug 1302725 - plugin-doorhanger.inc.css references alerticon-info-negative.png which has been changed to SVG, r=dao.

MozReview-Commit-ID: BUee8ZFWL2D