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
feat: upgrade to Chromium 73.0.3683.27 #16494
Conversation
d1e9302
to
ad96224
Compare
426c517
to
37ce80a
Compare
a1cb707
to
c6f2e7b
Compare
Will rebase once beta branch is cut in upstream, its real close. Lets merge once we have updated to beta release. |
c834c8a
to
a8c7a7a
Compare
@MarshallOfSound the
looks like its missing |
a8c7a7a
to
70e4744
Compare
70e4744
to
470d2be
Compare
Ignore lint errors, they should be fixed by #16906 |
470d2be
to
421afdf
Compare
MediaCaptureDevicesDispatcher::GetAudioCaptureDevices() { | ||
DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI)); | ||
if (is_device_enumeration_disabled_) | ||
return EmptyDevices(); | ||
return test_audio_devices_; |
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.
What's the intent behind returning an internal list instead of making a new empty one? This seems like a potential issue if this somehow became non-empty
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.
This is already behind a noop code path because of DisableDeviceEnumerationForTesting
. I am inclined to remove this condition all together, the goal of rewriting this was to see if the upstream MediaCaptureDevicesDispatcher
class can be reused with less patch.
// Get the default devices for the request. | ||
MediaCaptureDevicesDispatcher::GetInstance()->GetDefaultDevices( | ||
microphone_requested_, webcam_requested_, &devices); | ||
break; | ||
} | ||
case blink::MEDIA_DEVICE_UPDATE: { | ||
NOTREACHED(); |
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.
should we do something else with this event?
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.
It was added in https://chromium-review.googlesource.com/c/chromium/src/+/1354442. The feature seems specifically designed for chrome's screen sharing UI, can consider it for improvement in our desktop capture model once the issue goes public (the chromium issue has restricted view) and provides a bit more context.
atom/common/application_info.cc
Outdated
#include "chrome/common/chrome_version.h" | ||
#include "content/public/common/user_agent.h" | ||
|
||
std::string GetUserAgent() { |
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.
this should perhaps go in the atom
namespace? otherwise, it should have a comment about why it isn't
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.
Fixed.
&SetIsolatedWorldContentSecurityPolicy); | ||
dict.SetMethod("setIsolatedWorldHumanReadableName", | ||
&SetIsolatedWorldHumanReadableName); | ||
dict.SetMethod("setIsolatedWorldInfo", &SetIsolatedWorldInfo); |
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.
Did we update the docs for this? We should probably continue to support the old API as deprecated for 5-0-x
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.
@nornagon There is a separate PR to deprecate the current API in 5-0-x
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.
+ body->set_identifier(params->body->identifier); | ||
+ body->set_contains_sensitive_info(params->body->contains_sensitive_info); | ||
+ } | ||
+ |
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.
can we really get rid of all this stuff? that's great!
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.
network::ResourceRequestBody
got typemapped in https://chromium-review.googlesource.com/c/chromium/src/+/1395977 , which helped us get rid off these manual conversions. Side note: mojom typemaps are really cool feature :)
@@ -157,10 +157,13 @@ int ShowMessageBox(NativeWindow* parent_window, | |||
callEndModal:true]; | |||
|
|||
NSWindow* window = parent_window->GetNativeWindow().GetNativeNSWindow(); | |||
#pragma clang diagnostic push | |||
#pragma clang diagnostic ignored "-Wdeprecated-declarations" | |||
[alert beginSheetModalForWindow:window | |||
modalDelegate:delegate | |||
didEndSelector:@selector(alertDidEnd:returnCode:contextInfo:) | |||
contextInfo:nil]; |
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.
can we instead switch to using beginSheetModalForWindow:completionHandler:? here and below
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.
Yup that seems like the alternative, can we change this as a follow up ? There are cards for this in the project board.
|
||
# FIXME(deepak1556): workaround for https://crbug.com/924225 | ||
# remove this when clang roll 352138 lands. | ||
enable_precompiled_headers = false |
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.
can we remove this now?
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.
The change got landed in 74 https://chromium-review.googlesource.com/c/chromium/src/+/1436036
da12596
to
46a49b7
Compare
Release Notes Persisted
|
A maintainer has manually backported this PR to "5-0-x", please check out #16975 |
A maintainer has manually backported this PR to "5-0-x", please check out #16975 |
Description of Change
Refs https://github.com/electron/electron/projects/17
BREAKING CHANGE
Checklist
npm test
passesRelease Notes
Notes: upgrade to Chromium 73.0.3683.27