-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from Chromium 80.0.3987.163 to Chromium 81.0.4044.92 (1.7.x) #5204
Conversation
Upgrade from Chromium 80.0.3987.149 to Chromium 81.0.4044.69.
Fixed crash while importing from welcome ui
Fixes Clear Browsing Data dialog not showing.
Update patches from Chromium 81.0.4044.69 to Chromium 81.0.4044.83.
L10n for Chromium 81.
Upgrade patches from Chromium 81.0.4044.83 to Chromium 81.0.4044.92
Chromium change: https://chromium.googlesource.com/chromium/src/+/91ac1e4597667f679f99a9c58ada806b0c5c19b1 commit 91ac1e4597667f679f99a9c58ada806b0c5c19b1 Author: Andrew Grieve <agrieve@chromium.org> Date: Tue Mar 3 18:11:17 2020 +0000 Android: Speculative crash fix for DelayedScreenLockIntentHandler Stack is: Caused by: android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want? at android.app.ContextImpl.startActivity (ContextImpl.java: 952) at android.content.ContextWrapper.startActivity (ContextWrapper.java: 405) at org.chromium.chrome.browser.ChromeApplication.startActivity (ChromeApplication.java: 206) at org.chromium.chrome.browser.ChromeApplication.startActivity (ChromeApplication.java: 199) at org.chromium.chrome.browser.DelayedScreenLockIntentHandler.onReceive (DelayedScreenLockIntentHandler.java: 40) at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$LoadedApk$ReceiverDispatcher$Args (LoadedApk.java: 1550) ... From history on DelayedScreenLockIntentHandler, repro steps involve launching a page via NFC while locked. This restriction is listed as a new one in Android P: https://developer.android.com/about/versions/pie/android-9.0-changes-all#fant-required Bug: 1034440
Chromium change: https://chromium.googlesource.com/chromium/src/+/c9c4efe552830789d8602271c43c47830c8f2753 commit c9c4efe552830789d8602271c43c47830c8f2753 Author: Devlin Cronin <rdevlin.cronin@chromium.org> Date: Tue Jan 7 21:04:05 2020 +0000 [Extensions Cleanup] Move UnloadedExtensionReason to a new file Move the UnloadedExtensionReason enum to a new file, unloaded_extension_reason.h. There's no reason it needs to belong in extension.h, which is already quite large. Bug: 1038392
In addition to the same change on master (the affected code is not on master): 5495918
Same as this change in master: 24f70b8
817c1da
to
62310cd
Compare
CI run looks great, except on Android; there was a problem during
Going to rebase/re-run (both brave-core and brave-browser branches) as there have been some Android related CI items that have landed |
Re-run got the same error... will need to look at this |
Fix pushed for Android 😄 Thanks @SergeyZhukovsky for the help finding root cause |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
Fixes brave/brave-browser#8308
Fixes brave/brave-browser#8342
Fixes brave/brave-browser#8808
Fixes brave/brave-browser#8870
Fixes brave/brave-browser#8878
Fixes brave/brave-browser#8893
Fixes brave/brave-browser#9000
Related PR: brave/brave-browser#9103
Uplift from #4548
Uplift from #5018
Uplift from #5074
Uplift from #5075
Uplift from #5089
Uplift from #5150
Submitter Checklist:
npm run lint
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
Reviewer Checklist:
After-merge Checklist:
changes has landed on.