GitLab

8270: Fixes #8269 - remove old Dockerfile r=JohanLorenzo a=rpappalax
Co-authored-by: Richard Pappalardo <rpappalax@gmail.com>

8272: Update GeckoView (release) to 80.0.20200827204751 r=st3fan a=jonalmeida
Co-authored-by: Jonathan Almeida <jalmeida@mozilla.com>

8276: Import strings from android-l10n. r=jonalmeida a=mozilla-l10n-automation-bot

n/t
Co-authored-by: Mozilla L10n Automation Bot <release+l10n-automation-bot@mozilla.com>

8197: Closes issue #7762: Adds support for persisting/restoring downloads. r=csadilek a=Amejia481

Fenix pr https://github.com/mozilla-mobile/fenix/pull/14043

Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>

8252: Fennec MP import API r=rocketsroger a=grigoryk

Exposes the logins importer functions for the purpose of building an MP import UI in Fenix. No test coverage for this class, but there's also no new logic being added, just delegation to already well-tested methods.

Obtain the profile necessary for this class via `FennecProfile.findDefault(context, crashReporter)`.
Co-authored-by: Grisha Kruglov <gkruglov@mozilla.com>

8186: For #8185 - Add a new VerticalSwipeRefreshLayout r=NotWoods a=Mugurell

This comes to resolve many issues with SwipeRefreshLayout but based on a lot of
debugging. As a result the code is somewhat brittle.

Because we'd control responding to touches and updating the UI we need to be as
swift as possible and as such to differentiate between possible gestures I am
some simple layman's ways of doing this and GestureDetector / ScaleDetector
instances since they would add to the execution time and overall complexity,
and their callbacks would be hard to synchronize.
Co-authored-by: Mugurell <Mugurell@users.noreply.github.com>

8266: Closes #8264: Pass copy of breadcrumbs to crash reporting services r=pocmo a=rocketsroger
Co-authored-by: Roger Yang <royang@mozilla.com>

This comes to resolve many issues with SwipeRefreshLayout but based on a lot of
debugging. As a result the code is somewhat brittle.

Because we'd control responding to touches and updating the UI we need to be as
swift as possible and as such to differentiate between possible gestures I am
some simple layman's ways of doing this and GestureDetector / ScaleDetector
instances since they would add to the execution time and overall complexity,
and their callbacks would be hard to synchronize.

8262:  GeckoView update (nightly) (20200827-140422) r=pocmo a=MickeyMoz
Co-authored-by: MickeyMoz <sebastian@mozilla.com>

8257: Update GeckoView Nightly to 82.0.20200826032437. r=jonalmeida,rocketsroger a=pocmo

... and the final piece for upgrading!
Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>

8256:  Docs update (20200827-121225) [ci skip] r=pocmo a=MickeyMoz
Co-authored-by: MickeyMoz <sebastian@mozilla.com>

8222: Move and link top sites feature RFC. r=jonalmeida a=pocmo



8226: Closes #8209 - Use new onTouchEventForResult GV api r=pocmo a=Mugurell

Changes:
- previously NestedGV#onTouchEvent event would call onTouchEventForResult where
we would make possible the integration of GV in CoordinatorLayout.
Since NestedGV#onTouchEvent does not anymore call onTouchEventForResult I've
moved all code in onTouchEvent and then call onTouchEventForResult only for
ACTION_DOWN events as snorp recommended.
- we now must wait for onTouchEventForResult#GeckoResult<Int> and only then
call startNestedScroll(..) since otherwise when executing that method in
BrowserToolbarBottomBehavior we would return false since the MotionEvent is
at that time unhandled.
- only dispatch startNestedScroll and dispatchNestedPreScroll if GV returned
INPUT_RESULT_HANDLED.

In testing I saw most of the times GeckoResult resolves in < 5ms with bigger
timeouts showing a logarithmic growth. As such I think the change should be
imperceptible to users.

[video showing the same as before behavior in Fenix](https://drive.google.com/file/d/1WiQ5bXb-dBxYDA03snYSkxApxfhr7hgQ/view?usp=sharing

)
Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>
Co-authored-by: Mugurell <Mugurell@users.noreply.github.com>

8251: Import strings from android-l10n. r=pocmo a=mozilla-l10n-automation-bot

n/t
Co-authored-by: Mozilla L10n Automation Bot <release+l10n-automation-bot@mozilla.com>

7705: For #7700 - Use the website favicon in save login dialog r=Amejia481 a=BranescuMihai
Co-authored-by: Mihai Branescu <branescu.mihai@gmail.com>

7795: Issue #6429: Add container page action icon in the browser toolbar r=Amejia481 a=gabrielluong
Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>

8243: Closes #8242: Keep latest breadcrumbs r=pocmo a=rocketsroger
Co-authored-by: Roger Yang <royang@mozilla.com>

8121: Issue #7867: Move EngineSession from SessionManager to BrowserState. r=csadilek a=pocmo

Fenix PR: https://github.com/mozilla-mobile/fenix/pull/13933
R-B PR: https://github.com/mozilla-mobile/reference-browser/pull/1292

Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>

Changes:
- previously NestedGV#onTouchEvent event would call onTouchEventForResult where
we would make possible the integration of GV in CoordinatorLayout.
Since NestedGV#onTouchEvent does not anymore call onTouchEventForResult I've
moved all code in onTouchEvent and then call onTouchEventForResult only for
ACTION_DOWN events as snorp recommended.
- we now must wait for onTouchEventForResult#GeckoResult<Int> and only then
call startNestedScroll(..) since otherwise when executing that method in
BrowserToolbarBottomBehavior we would return false since the MotionEvent is
at that time unhandled.
- only dispatch startNestedScroll and dispatchNestedPreScroll if GV returned
INPUT_RESULT_HANDLED.
- Ignored "ClickableViewAccessibility" since NestedGeckoView is not intented
to be clickable, but rather the elements from the webpage displayed.

In testing I saw most of the times GeckoResult resolves in < 5ms with bigger
timeouts showing a logarithmic growth. As such I think the change should be
imperceptible to users.

8239: Update GeckoView (Beta) to 81.0.20200825191644. r=Amejia481 a=pocmo

Follow-up from #8221. We got a new beta build and now we can update safely. :)
Co-authored-by: Sebastian Kaspari <s.kaspari@gmail.com>

8241: Issue #8216: Add photonViolet50, photonDarkGrey40 and photonLightGrey50 to photon_colors r=jonalmeida a=gabrielluong
Co-authored-by: Gabriel Luong <gabriel.luong@gmail.com>

Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>

Issue #8121: Replace MigrationStore with MigrationContext and prevent usage outside of a Middleware.

* Before executing the reducer chain we now verify that we are on the store thread and throw if we are on a different thread.
* MigrationContext now provides a store property that returns the underlying Store instance. This can be used to pass it to
  other components and threads that are not part of the Middleware.
* Fixed existing Middleware implementations to use the MiddlewareContext or pass the actual Store instance around.

8198: For #7134 - Dismiss the current select login prompt request in LoginPicker r=Amejia481 a=ekager
Co-authored-by: ekager <ekager@mozilla.com>

8233: Close #8232: Remove firebase-core dependency from lib-push-firebase r=pocmo a=jonalmeida

For Cloud Messaging, we no longer need `firebase-core` as a dependency. This removes unneeded services that can run on the device.
Co-authored-by: Jonathan Almeida <jalmeida@mozilla.com>

8238:  Docs update (20200826-121903) [ci skip] r=pocmo a=MickeyMoz
Co-authored-by: MickeyMoz <sebastian@mozilla.com>