Revert "Address even more lint errors."
This reverts commit e98ee991b34d318e671c644d63daec53902e68ff.
Revert "Update to Gradle 6.6.1."
This reverts commit cdda701c8f2be6c0486ddf1494885accf78aab00.
Revert "Address lint errors."
This reverts commit 26cb5b27bc2be672c89e7e0c63eeeda9f64c0d08.
Revert "Move JNA configuration to root project."
This reverts commit 694ef37cc30e727f3ec5d275c0e9583385980a43.
Revert "Issue https://github.com/mozilla-mobile/android-components/issues/8319: Update to Kotlin 1.4, Coroutines 1.3.9 and Android lint 27.0.1."
This reverts commit ad675c35e794050dbf8514a2d2fe7506ce0c546c.
Revert "Update Glean to 33.0.4."
This reverts commit 4731c4e2fa52d40f4062a47f02078ca0c85de632.
Revert "Update Glean to 33.0.0."
This reverts commit 352cf88a4d4bad64330d0ec997814fd8b13928c2.
Revert "Update Gradle to 6.1.1."
This reverts commit 18e88aa1a2528b10f7d81ff9dbf1df094071b6ce.
Revert "Update Android Gradle Plugin to 4.0.1."
This reverts commit f915a3b47b0f5584889ff62a80c9642bccfa36ce.
* Instead of keeping the EngineSessionState inside EngineSession, we now always attach it to EngineState and also do not
clear it anymore.
* If the content process gets killed we now just suspend affected EngineSession instances. They will automatically and
lazily get restored from the last EngineSessionState once needed.
* On a content process crash we now mark the EngineState as crashed and suspend the EngineSession. We will not restore
the EngineSession until explicitly restored by the application.
- a WebAppInterceptor is needed to redirect to a separate WebApp
activity
- the manifest dao currently reports a web app as installed when it was
last used before the deadline / expiration time. This is the oposite
of what it's supposed to do.
- The intent extension should also hold an override URL so a WebApp
intent can be launched with a deeplink.
- The WebAppIntentProcessor currently launches new sessions for each
intent. This will break user expectations when they start to be
switched to a already running WebApp activity but loose their session.
- we need a cache for currently installed web app scopes, so we don't
have to do blocking IO during page load.
There are currently 3 Views interested in handling user's MotionEvents:
- GeckoView which renders web content
- SwipeRefreshLayout which handles pull down to refresh
- BrowserToolbar which can be dynamically hidden
Each of them have different behaviours based on different conditions so I
- removed the coupling of BrowserToolbar and Geckoview from `NestedGeckoView`.
It's `onTouchEventForResult` will now only set behaviour for GeckoView.
- created a new EngineView enum to expose the `PanZoomController` possible
result of how a specific user touch was handled to any components that have a
reference to an instance of EngineView without the need to have
`concept-engine` as a dependency.
- implemented specific behaviour in `SwipeRefreshFeature` for the pull down to
refresh functionality and in the `BrowserToolbarBottomBehavior` for the dynamic
navigation bar functionality.
Mapped PanZoomController's INPUT_RESULT to a new enum in order to not enforce
the need of including geckoview as a dependency in all components interested in
how a user's `MotionEvent` was handled and also because webview doesn't expose
such values so we needed a wrapper for it's handled or not boolean return.
6182: https://github.com/mozilla-mobile/android-components/issues/3832: Add support for additional headers when loading url r=pocmo a=psymoon
6197: Import strings from android-l10n. r=jonalmeida a=mozilla-l10n-automation-bot
n/t
6270: For https://github.com/mozilla-mobile/android-components/issues/6269: Notify active sessions when all exceptions are removed. r=Amejia481 a=ValentinTimisica
I also updated the tests accordingly.
Made this change because the tracking protection icon is not updated after the
exceptions are removed.
6286: Closes https://github.com/mozilla-mobile/android-components/issues/6281: Do not automatically dismiss confirm dialogs r=Amejia481 a=csadilek
The feature to automatically dismiss can maybe be made more robust to not be affected by lifecycle changes (https://github.com/mozilla-mobile/android-components/issues/6281#issuecomment-599739212), but in either case we don't want to automatically dismiss confirmation dialogs, as these require user interaction before the next page load anyway.
Similar fix to: https://github.com/mozilla-mobile/android-components/pull/5704/
Co-authored-by: Simon Chae <chaesmn@gmail.com>
Co-authored-by: Mozilla L10n Automation Bot <release+l10n-automation-bot@mozilla.com>
Co-authored-by: ValentinTimisica <valentin.timisica@softvison.ro>
Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
