chore: bump chromium to f1d9522c04ca8fa0a906f88ababe9 (master)#18648
chore: bump chromium to f1d9522c04ca8fa0a906f88ababe9 (master)#18648MarshallOfSound merged 128 commits intomasterfrom
Conversation
c60c1f7 to
b45de03
Compare
854355e to
5a8dd1e
Compare
There was a problem hiding this comment.
If we're doing this we need to add it to the breaking-changes document and add a TODO to deprecate in Electron 6
EDIT: For context this was supposed to be a comment on dcf06eb
GitHub put it as a review comment though 🤷♂
|
@MarshallOfSound i've added it to breaking changes and we should note its deprecation in the 6.0.x release notes (where's the right place for that?) I'm not sure this warrants a programmatic deprecation warning on the console as that would mean a fair chunk of work to wrap the API in a JS wrapper so that we could call the relevant JS deprecation helper, when currently it's just a direct C++ call. It's a relatively minor API and I think it'd be fine to just document the deprecation—thoughts? |
|
ARM build is failing due to https://crbug.com/972766, stalling until a workaround or fix is implemented. |
|
wait up... why is swiftshader building at all? https://github.com/electron/electron/blob/master/patches/chromium/revert_build_swiftshader_for_arm32.patch this should be preventing it from being built |
| } | ||
|
|
||
| shm_mapping_ = shm.Map(); | ||
| shm_mapping_ = region.Map(); |
There was a problem hiding this comment.
While shm_mapping_ is retained by the class, the readable region is only available for the scope of this function, do we want to retain it as well ?
shm_region_ = std::move(region);
I am not sure whats the reason behind retaining shm_mapping_ , /cc @brenca who wrote the initial implementation.
There was a problem hiding this comment.
Me either, this code is a mystery to me. The tests pass though? 😬
There was a problem hiding this comment.
linux seemed to have related failure https://circleci.com/gh/electron/electron/229118?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link , rerunning it now.
There was a problem hiding this comment.
The linux ones are failing consistently.
There was a problem hiding this comment.
ah... you're right. okay, i guess we'll have to hold off on merging then.
|
I think the arm node inspector failures are a flake ? Since there wasn't a node bump in this PR 🤔 |
|
maybe... but both 64 and 32-bit failed the same way. i'll try rerunning. |
4145564 to
9aa8313
Compare
| if (!HasMainProcessKey() && | ||
| base::EndsWith(path.value(), " Helper", base::CompareCase::SENSITIVE)) { | ||
| (base::EndsWith(path.value(), " Helper", base::CompareCase::SENSITIVE) || | ||
| base::EndsWith(path.value(), content::kMacHelperSuffix_renderer, |
There was a problem hiding this comment.
kMacHelperSuffix_plugin not allowed?
There was a problem hiding this comment.
@nornagon that I know of we are not using the plugin helper; though I guess we could add it here for completeness
There was a problem hiding this comment.
@jkleinsc it will be used when pepper plugins are loaded. https://chromium.googlesource.com/chromium/src/+/4be2698e4784b68198d1062a54942ae232c57c24
There was a problem hiding this comment.
@deepak1556 ah I forgot about those. I'll add that conditional.
Can be removed once CL lands upstream. Refs: https://chromium-review.googlesource.com/c/chromium/src/+/1685993
This test requires a secure origin so we fake one. Refs: https://chromium-review.googlesource.com/c/chromium/src/+/1657952
|
No Release Notes |
Updating Chromium to f1d9522c04ca8fa0a906f88ababe9 (lkgr).
See all changes in bd6aad6a4b37dad7aae42fec349e9..f1d9522c04ca8fa0a906f88ababe9
Notes: no-notes