8000 feat: Upgrade to Chromium 71.0.3578.98 by deepak1556 · Pull Request #15966 · electron/electron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: Upgrade to Chromium 71.0.3578.98 #15966

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

Merged
merged 53 commits into from
Jan 12, 2019
Merged

feat: Upgrade to Chromium 71.0.3578.98 #15966

merged 53 commits into from
Jan 12, 2019

Conversation

deepak1556
Copy link
Member
@deepak1556 deepak1556 commented Dec 6, 2018

Description of Change

Refs https://github.com/orgs/electron/projects/26

BREAKING CHANGE

Checklist

  • PR description included and stakeholders cc'd
  • npm test passes
  • tests are changed or added
  • relevant documentation is changed or added
  • PR title follows semantic commit guidelines

Release Notes

Notes: Upgrade to Chromium 71.0.3578.98

@deepak1556 deepak1556 requested review from a team December 6, 2018 01:45
- # Enables Widevine key system support. Enabled by default in Google Chrome or
- # on Android. Can be optionally enabled in Chromium.
- enable_widevine = is_chrome_branded || is_android
+ # Allow Widevine key system support in Chromium.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we don't need to patch this comment

@deepak1556 deepak1556 force-pushed the chromium-upgrade/71 branch 2 times, most recently from 11f7703 to c557736 Compare December 7, 2018 20:21
@zcbenz zcbenz force-pushed the chromium-upgrade/71 branch from 06cba7c to ec4c329 Compare December 14, 2018 08:50
@zcbenz
Copy link
Contributor
zcbenz commented Dec 14, 2018

I'm rebasing this branch to fix conflict with webview fixes.

@zcbenz zcbenz force-pushed the chromium-upgrade/71 branch from ec4c329 to 8e6ea7d Compare December 14, 2018 10:53
@deepak1556 deepak1556 force-pushed the chromium-upgrade/71 branch 2 times, most recently from 479c3cd to 5a24bfd Compare December 25, 2018 01:36
@nornagon nornagon force-pushed the chromium-upgrade/71 branch from b82b054 to 957a3d3 Compare January 3, 2019 22:01
@deepak1556 deepak1556 changed the title [WIP] feat: Upgrade to Chromium 71.0.3578.80 [WIP] feat: Upgrade to Chromium 71.0.3578.98 Jan 4, 2019
@deepak1556 deepak1556 force-pushed the chromium-upgrade/71 branch 3 times, most recently from c1e0e1d to c8e461b Compare January 8, 2019 09:59
@@ -182,30 +183,21 @@ void AtomSandboxedRendererClient::DidCreateScriptContext(
!IsDevToolsExtension(render_frame))
return;

// Wrap the bundle into a function that receives the binding object as
// argument.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this comment still accurate?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup the per process loader essentially does the same, it runs the provided source under a scope that has these arguments in the global variable.

v8::Isolate* isolate = context->GetIsolate();
v8::HandleScope handle_scope(isolate);
v8::Context::Scope context_scope(context);

// Wrap the bundle into a function that receives the isolatedWorld as
// an argument.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this comment still accurate?

@deepak1556 deepak1556 changed the title [WIP] feat: Upgrade to Chromium 71.0.3578.98 feat: Upgrade to Chromium 71.0.3578.98 Jan 10, 2019
@deepak1556 deepak1556 requested review from nornagon and zcbenz January 10, 2019 04:46
Copy link
Contributor
@nornagon nornagon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with some comments


namespace {

napi_value Print(napi_env env, napi_callback_info info) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this called Print? Perhaps it should be called Echo?

try {
window.localStorage
} catch (e) {
message = e.message
const {ipcRenderer} = require('electron')
ipcRenderer.send('local-storage-response', e.message)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like it won't send a message back if it doesn't throw, which will just make the test time out. Let's make tests fail fast & with useful error messages rather than dealing with yet another "test timed out" failure.

@nornagon nornagon force-pushed the chromium-upgrade/71 branch from f41f13b to 7fa67e1 Compare January 11, 2019 19:54
deepak1556 and others added 25 commits January 11, 2019 13:55
Due to the migration to Custom Elements V1, the WebView element has to
be defined in the DOM's context. To order to make WebView work with the
contextIsolation, the definition of WebView element has been moved to a
separate file.
per frame scheme previlege api are no longer available,
scheme needs to be registered on the browser side with
AtomContentClient::AddAdditionalSchemes
@nornagon nornagon force-pushed the chromium-upgrade/71 branch from 7fa67e1 to 8bec8e5 Compare January 11, 2019 21:56
@nornagon nornagon merged commit 52fe92d into master Jan 12, 2019
@release-clerk
Copy link
release-clerk bot commented Jan 12, 2019

Release Notes Persisted

Upgraded to Chromium 71.0.3578.98.

@nornagon nornagon deleted the chromium-upgrade/71 branch January 12, 2019 01:01
akisctx pushed a commit to akisctx/electron that referenced this pull request Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0