chore: bump chromium to 122.0.6194.0 (29-x-y)#40872
Merged
Conversation
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5079532 minor manual changes to match upstream changes Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5094777 Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5054299 Update patch to upstream changes in print_view_manager_base.cc. CC @codebytere for 👀 Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5083156 no manual changes; patch applied with fuzz 1 Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5087072 minor manual changes to match upstream changes Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/4960481 no manual changes; patch applied with fuzz 2 Co-authored-by: Charles Kerr <charles@charleskerr.com>
…ting.patch Xref: https://chromium-review.googlesource.com/c/v8/v8/+/5076902 Xref: https://chromium-review.googlesource.com/c/v8/v8/+/5096253 The `bailout_value` variable, which allowed us to fail gracefully in these macros, has been removed upstream. This raises the temperature on #40741 ... Since we don't have a bailout value, return a default-constructed instance of whatever the return type is of the function that invokes the macro. Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5068017 It appears it is not used by anything within Chromium or outside. Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5066872 The copy construtor is more expensive and has been removed upstream Co-authored-by: Charles Kerr <charles@charleskerr.com>
…dispatcher_ Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5055146 Co-authored-by: Charles Kerr <charles@charleskerr.com>
…Type>::ToV8() Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5096614 Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5075094 Previously we could pass a routing ID into the spellcheck methods. This ID arg has been replaced with a SpellCheckHost& arg. We can get the SpellCheckHost from an accessor in SpellCheckProvider, which was already being created on a per-render-frame basis in RenderClientBase. This commit adds a RenderFrame-to-SpellCheckProvider accessor in RenderClientBase so that it can be used to get that needed SpellCheckHost. Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5074445 Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5031312 upstream reverted this change Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Co-authored-by: PatchUp <73610968+patchup[bot]@users.noreply.github.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5115241 Co-authored-by: Charles Kerr <charles@charleskerr.com>
… converter Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5049989 Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
….patch Co-authored-by: Charles Kerr <charles@charleskerr.com>
…ting.patch The previous experiment of removing the DCHECK in 3509378 was a huge failure. We either need to either: A) use upstream as-is and fix the DCHECK failure, or B) revert https://chromium-review.googlesource.com/c/v8/v8/+/5076902 too C) find some other workaround This commit is the first half of option A, removing the patch to use upstream as-is. Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5085619 minor manual changes to match upstream changes Co-authored-by: Charles Kerr <charles@charleskerr.com>
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5120922 minor manual changes to match upstream changes Co-authored-by: Charles Kerr <charles@charleskerr.com>
…g.patch Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5041595 no manual changes; patch applied with fuzz 1 Co-authored-by: Charles Kerr <charles@charleskerr.com>
Co-authored-by: Charles Kerr <charles@charleskerr.com>
https://chromium-review.googlesource.com/c/chromium/src/+/5100709 Co-authored-by: deepak1556 <hop2deep@gmail.com>
https://chromium-review.googlesource.com/c/chromium/src/+/5019703 Co-authored-by: deepak1556 <hop2deep@gmail.com>
https://chromium-review.googlesource.com/c/chromium/src/+/5024173 Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
…api_changes.patch Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
https://chromium-review.googlesource.com/c/chromium/src/+/5119048 Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
https://chromium-review.googlesource.com/c/chromium/src/+/5059112 Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
https://chromium-review.googlesource.com/c/v8/v8/+/5050065 Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: deepak1556 <hop2deep@gmail.com>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
codebytere
approved these changes
Jan 4, 2024
|
Release Notes Persisted
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #40750
See that PR for details.
Notes: Updated Chromium to 122.0.6194.0.