-
Notifications
You must be signed in to change notification settings - Fork 898
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 88.0.4315.7 to Chromium 88.0.4324.51. #7408
Conversation
97d10e0
to
cead120
Compare
@@ -403,9 +403,6 @@ void AdNotificationViewMD::UpdateControlButtonsVisibilityWithNotification( | |||
UpdateControlButtonsVisibility(); | |||
} | |||
|
|||
void AdNotificationViewMD::ButtonPressed(views::Button* sender, |
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.
Were changes in ui/brave_ads
intentional as these will likely break ads?
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.
Yes, these are due to the Chromium change: https://chromium.googlesource.com/chromium/src/+/37cb433bb3d86231ee0c37cdd8a08f31ab35f172 (views::ButtonListener has been removed).
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.
++
886c639
to
7943ccb
Compare
Added: - /usr/lib/swift - @executable_path/../Frameworks This to get around the error: brave_rewards_ios_tests.app (22597) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Crash: brave_rewards_ios_tests (22597): dyld: Using shared cache: 59E5DB8B-B935-310F-81BF-FB7488068748 Library not loaded: @rpath/libswiftCore.dylib
Chromium change: https://source.chromium.org/chromium/chromium/src/+/f8ddb215c89b090a11494830f28b6b630167a7a8 commit f8ddb215c89b090a11494830f28b6b630167a7a8 Author: Javier Ernesto Flores Robles <[email protected]> Date: Mon Nov 9 22:09:33 2020 +0000 [iOS][WidgetKit] Enable extension by default in ToT Bug: 1138702
Added a gap between Chromium and our histogram values for ContentSettingsType enum values. This is needed so that we don't have collisions when new values are added to the enum and the array upstream.
This prevents crash on iOS when AUTOPLAY isn't registered (unclear why ATM). Also, removes unneeded header include.
CI:
Merging. |
|
||
int ContentSettingTypeToHistogramValue(ContentSettingsType content_setting, | ||
size_t* num_values) { | ||
DCHECK(static_cast<int>(ContentSettingsType::NUM_TYPES) < kBraveValuesStart); |
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.
jfyi this could be static_assert
Upgrade from Chromium 88.0.4315.7 to Chromium 88.0.4324.51.
Upgrade from Chromium 88.0.4315.7 to Chromium 88.0.4324.51.
Upgrade from Chromium 88.0.4315.7 to Chromium 88.0.4324.51.
Fixes brave/brave-browser#13103
Related PR: brave/brave-browser#13143
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed).Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on.
Test Plan: