chromium
| Legend: | Passed | Failed | Running | Exception |
Remove requirement for context sharing enabled in pinned tabs cause it is broken
Bug: 433154265
Change-Id: I525b779c1ddf56f22ae7541d588d1f7095f1357d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782100
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491227}
Move wtf/wtf_size_t.h to "blink" namespace
This CL has no behavior changes.
Bug: 422768753
Change-Id: Ied36b5e69eba9af71f721a968b6a9e528f764da3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778748
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491226}
Disable "UseOriginalDomOffsetsForOffsetMap" flag for production
Bug: 430508617
Change-Id: I937cd78228853ffd9f64b125eb07b63af156c5f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779665
Reviewed-by: Koji Ishii <kojii@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491225}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753316103-aba96dd5a3d6f9357486a4c909c3e2d4a07dacbe-f0b2e763b0287bb864a26296f4645584053d65c8.profdata to chrome-android64-main-1753321021-f3a0a1a87c86255b70c55837442535504c6fb4b7-53f756a550388a4308378ce3b24df0593abf62d3.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-android-arm64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ieea074c23196b3365bf88767e1bb24446204b818
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782288
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491224}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-main-1753293557-62db5e51f0ed9367feb669a6c23db5eb90b26466-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-mac-main-1753314684-f8601a81b6179e9dc0abd448fe34eea60cec9315-701ac6259b6182382cbebd32369b58c64a99d12f.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I210696ae84f157dbd2e98d60e655e160c0c28484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782224
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491223}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-main-1753271698-dba84a7f93b583ffd4f2cb2ad6c063c564f9f972-faf031012b7e5c3f8eae3fda40f75490f508e42d.profdata to chrome-win32-main-1753293557-1e5f5de80b7fe2c07413d277b32fb2f829caace6-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win32-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ia6827cfd16335b8e5fb907c37b5d5856147d101e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781815
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491222}
Refactor: split module templates into separate file.
This will allow in the future for each platform's config to be stored in
a separate, autogenerated file.
Bug: 425527533
Change-Id: I6a6a69646b29f1a4a6238e8b8375b0f88ef5ea07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778646
Commit-Queue: Matt Stark <msta@google.com>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Junji Watanabe <jwata@google.com>
Cr-Commit-Position: refs/heads/main@{#1491221}
Roll src-internal from 69aa4b323eee to c304aaac9c9d (3 revisions)
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/69aa4b323eee..c304aaac9c9d
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC chrome-browser-infra-team,suzukikeita@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Bug: chromium:1423117
Tbr: suzukikeita@google.com
Change-Id: Ib53851d600e9d1b7696520fb604eb9b26153bfa2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782287
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491220}
[FSA] Add implementation for "write" permission mode
- Add `blink::mojom::FileSystemAccessPermissionMode::kWrite` and make
the enum a standalone file to resolve dependency issues.
- Update `mojom::FileSystemAccess*Handle::GetPermissionStatus(bool)`
and `mojom::FileSystemAccess*Handle::RequestPermission(bool)` to take
`FileSystemAccessPermissionMode` instead of `bool writable`.
- Pipe down kWrite to content layer and update
`FileSystemAccessHandleBase::DoRequestPermission()` and
`FileSystemAccessHandleBase::DoGetPermissionStatus()` accordingly.
- The new permission mode is NOT surfaced to any IDL yet. And it should
be no impact to existing FileSystemAccess APIs.
Bug: 40276567
Change-Id: Ic9888cf389a553dd06b6d9127f00a9d0087deae8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6767698
Reviewed-by: Austin Sullivan <asully@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Ming-Ying Chung <mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491219}
Updating trunk VERSION from 7315.0 to 7316.0
* This is an automated release commit.
* Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
Change-Id: I58d55981a9b46b3f0ae111d67a8915b03daf4f91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777135
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491218}
Roll Chrome Win ARM64 PGO Profile
Roll Chrome Win ARM64 PGO profile from chrome-win-arm64-main-1753293557-65e43a6a29efc70373fd94b97be79d2b1b99b0ec-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-win-arm64-main-1753314684-2bbba4c72c63fafcd910a4d1123a071af9dd5c85-701ac6259b6182382cbebd32369b58c64a99d12f.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win-arm64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I155269176e0cc63ee2a5cb4521afe16eda4b64c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782283
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491217}
webnn: support run conformance test by specified test name
This CL introduces the 'tc' parameter to run conformance tests of
operators by specified test name. For example, navigating to this link
[1] only runs "abs float32 1D tensor" test, and link [2] only runs "abs
float32 1D tensor" and "abs float32 4D tensor" two tests. Besides, it's
to run all abs conformance tests without 'tc' parameter. This feature is
useful for driver developer to focus on debugging a particular failure
test case.
[1] https://wpt.live/webnn/conformance_tests/abs.https.any.html?device=cpu&tc=abs float32 1D tensor
[2] https://wpt.live/webnn/conformance_tests/abs.https.any.html?device=cpu&tc=abs float32 1D tensor&tc=abs float32 4D tensor
Bug: 433326681
Change-Id: Ic23cce2f652c7501a2392475490dd722ca9d3044
Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6776105
Commit-Queue: Feng Dai <feng.dai@intel.com>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Auto-Submit: Feng Dai <feng.dai@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491216}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known. This CL has no
behavior changes.
All changes should be correct and no behaviour changes in patchset 1,
however the plan is to follow up and remove the redundant size
parameters. To this effect in patchset 2 we've added CHECKS and renames
to note the fact the size is believed to be redundant. This was done
through AI and should be carefully checked, but the CHECKS are not fatal
and thus if unsure should be fine to land and remove after reports of
the crashes.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with `git cl split --target-range 8 32 --max-depth=2
--no-reviewers -d ~/description.txt`
This covers directories: third_party/blink/renderer/core/streams
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I671938cc544cedb53fd7b53f7feedafd4ad09064
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6734602
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491215}
Roll Chrome Android Desktop x64 PGO Profile
Roll Chrome Android Desktop x64 PGO profile from chrome-android-desktop-x64-main-1753293557-75f1c7bff7db606385a00be835a600d13f75c72f-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-android-desktop-x64-main-1753314684-fca3aa394d92074d0550999c1889d710de7f353b-701ac6259b6182382cbebd32369b58c64a99d12f.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-android-desktop-x64-chromium
Please CC al-clank-pgo@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iddd3b8c3052a8012d8a097feab608560ed583742
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782282
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491214}
Revert "Set AutofillEnableShowSaveCardSecurelyMessage enabled by default"
This reverts commit 961eee164eeca76b9b184e5f2270e5cbe60d2a29.
Reason for revert: Suspect it broke test:
ChromePaymentsAutofillClientTest.ShowSaveCreditCardToCloud_CardSaveTypeIsWithCvc_RequestsBottomSheet
on:
https://ci.chromium.org/ui/p/chrome/builders/ci/android-desktop-16-x64-rel-al-emu-tests/2158/overview
Bug: b:409603749
Original change's description:
> Set AutofillEnableShowSaveCardSecurelyMessage enabled by default
> and remove fieldtrial testing config.
>
> Bug: b:409603749
> Change-Id: I809412f164f597f6df94508c8e7b5867f47f606f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781879
> Commit-Queue: Qihui Zhao <qihuizhao@google.com>
> Reviewed-by: Olivia Saul <osaul@google.com>
> Cr-Commit-Position: refs/heads/main@{#1491097}
Bug: b:409603749
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I41dec64a167351b2f795216960efa9b1c399e016
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778012
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491213}
[webaudio-testharness] Migrate iirfilter-getFrequencyResponse.html
This CL rewrites the IIRFilterNode getFrequencyResponse() test to use
testharness.js instead of the legacy audit.js framework. The logic and
thresholds remain unchanged, preserving test validity. This migration
helps reduce dependencies on audit.js and aligns with Web Platform Test
standards.
Bug: 396477778
Change-Id: I093a0ccd8792a5813c47e46148b09c7410474e1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6688066
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Auto-Submit: Punith Nayak <punithbnayak@chromium.org>
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Commit-Queue: Punith Nayak <punithbnayak@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491212}
[webaudio-testharness] Migrate audiochannelsplitter.html
This CL replaces usage of audit.js in
third_party/blink/web_tests/webaudio/the-audio-api/audiochannelsplitter.html
with testharness.js, preserving existing test logic and comments.
Bug: 396477778
Change-Id: I82a31c746da93d844cbd3eedc28490fe84e368d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6709825
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Punith Nayak <punithbnayak@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491211}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753311747-b7db342dc73c8647d1539bd995ff39bbc6b6f6ff-3667e2e53a3cce646f3710a8408aed305c3892ea.profdata to chrome-android64-main-1753316103-aba96dd5a3d6f9357486a4c909c3e2d4a07dacbe-f0b2e763b0287bb864a26296f4645584053d65c8.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-android-arm64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iff7bdd168f23f588b9c4a6ea8011bc90ba2e9b8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782281
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491210}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-main-1753271698-d867931a2e58acaf23629c343ce4a72e3832d46c-faf031012b7e5c3f8eae3fda40f75490f508e42d.profdata to chrome-win64-main-1753282773-9ff150ff83e0015e7bf29c3a08593d4b1b6cc8ff-32093f0b1887f58ac9849a01921abe9ebdd6e770.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I1fead25d8529ae5e23ce76d6525a257ca9be8b0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781804
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491209}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753307944-0293fce53192d21b2e00d09c92bd45b280f2cc2c-4c40e1c20da2b4ff6ad23a2da704b7bcbf0acf22.profdata to chrome-mac-arm-main-1753314684-7b1d8af4b17e9003032919fefcee7cc879b83668-701ac6259b6182382cbebd32369b58c64a99d12f.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-arm-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I5f88f37fc5d3e2f07b890c63a2fdf82648eacfac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782227
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491208}
disable secagentd.FileEvents tests on trogdor
Bug: 433816171
Change-Id: I3172001ddd0d3ced64ae7bdc9ee2e0e5b13b102c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782061
Auto-Submit: Jeffrey Young <cowmoo@google.com>
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491207}
Disable GetLastActiveBrowserWindowInterface_ReturnsLastActive
Bug: 431671448
Change-Id: I424174f8547167ebb695abde2426c9375becfe65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781451
Reviewed-by: Keita Suzuki <suzukikeita@chromium.org>
Owners-Override: Keita Suzuki <suzukikeita@chromium.org>
Auto-Submit: Nick Birnie <birnie@google.com>
Commit-Queue: Keita Suzuki <suzukikeita@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491206}
NavigationThrottleRunner2: Initial placeholder implementation
This change introduces a new flag-guarded NavigationThrottleRunner2
implementation, which is intended to replace the current one in the
future.
NavigationThrottleRegistryImpl owns a virtual interface to the runner,
and actual instance can be switched behind a base::Feature flag.
This is the first step to introduce the implementation switch, and
subsequent CLs will implement the new behaviour in
NavigationThrottleRunner2.
Bug: 422003056
Change-Id: Ife180cb0284bbdd94a7c420e99073ab932987e55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777133
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491205}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known.
This CL has no behavior changes.
All changes should be correct and no behaviour changes in patchset 1, however the plan is to follow up and remove the redundant size parameters. To this effect in patchset 2
we've added CHECKS and renames to note the fact the size is believed to be redundant. This was done through AI and should be carefully checked, but the CHECKS are not fatal and thus if unsure should be fine to land and remove after reports of the crashes.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with
`git cl split --target-range 8 32 --max-depth=2 --no-reviewers -d ~/description.txt`
This covers directories:
remoting
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I7e86bbf995c7c3c20e81b6042cf486608034b090
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6737283
Reviewed-by: Joe Downing <joedow@chromium.org>
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491204}
Roll Chromium Variations from o7FVvr7bQQu5penh4... to HTAVu9JCOAeq43Tt-...
https://chrome-infra-packages.appspot.com/p/chromium/chrome/test/data/variations/cipd/+/HTAVu9JCOAeq43Tt-jP4PtKydpWS5lVKWZ-Qgx2HUv0C
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromium-variations-chromium
Please CC chrome-metrics-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium Variations: https://bugs.chromium.org/p/chromium/issues/entry
To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Bug: None
Tbr: chrome-metrics-team@google.com
Change-Id: I03c22f7ed0dda5f4df325c6c466afee31335edcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782226
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491203}
ThreadTicks GetForThread should include kernel time for arm64
Modify ThreadTicks::GetForThread to return user time + kernel time
instead of just user time.
Bug: 433551588
Change-Id: I52141f94fa5824601a519f5a2b34cd00cee34e9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781007
Commit-Queue: Chris Davis <chrdavis@microsoft.com>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491202}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known.
This CL has no behavior changes.
All changes should be correct and no behaviour changes, however the plan
is to follow up and remove the redundant size parameters. To this effect
we've added CHECKS and renames to note the fact the size is believed to
be redundant.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with
`git cl split --target-range 8 32 --max-depth=2 --no-reviewers -d ~/description.txt`
This covers directories:
mojo
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I037f3f84dadc1f344525406b43d3e0719781b1be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6734599
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: Fred Shih <ffred@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491201}
Roll GoogleTest from 7e17b15f1547 to 32f9f4c82afa (1 revision)
https://chromium.googlesource.com/external/github.com/google/googletest.git/+log/7e17b15f1547..32f9f4c82afa
2025-07-23 absl-team@google.com Skip the predicate on SIGSEGV in death-test on Android builds with API level <= 23.
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/googletest-chromium-autoroll
Please CC asully@google.com,jonathanjlee@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_cfi_rel_ng;luci.chrome.try:win-chrome
Tbr: asully@google.com,jonathanjlee@google.com
Change-Id: I980c1cbef230160ade0b387230ff867b5697be2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781812
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491200}
[exit-time-destructors] Exclude target with warnings
This CL is part of number of CLs disabling `-Wexit-time-destructors`in
places where this warning is going off. This will allow having this
warning enabled-by-default across the codebase, whilst documenting the
places where corrections for this warning are necessary.
Bug: 40031409, 430332953
Change-Id: I0a306ea43722c4dd1ba4d59afdf6030492aa87b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777947
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Claudio DeSouza <cdesouza@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491199}
Rollback to pdf library alpha06
Revert back due to unresolved regressions. See bug below.
Will add local modifications back once the change is picked up by the
roller.
See http://crrev.com/c/6669737
Bug: 424250731
Change-Id: I4c9d9738615218f4fb8acb6d8166fe77b9510a73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782318
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Shu Yang <shuyng@google.com>
Cr-Commit-Position: refs/heads/main@{#1491198}
NTP Promos: Use ordering policy when generating promo lists
Bug: 428035923
Change-Id: I7218dcce4ed5c9e6fad5b9d360fef0d63ecda590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780056
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491197}
WebNN: Ensure scale and zeroPoint rank is equal to input rank
This CL implements the WebNN spec change [1] that requires the scale
and zeroPoint for quantizeLinear and dequantizeLinear ops have the
the same rank as input.
[1]: https://github.com/webmachinelearning/webnn/pull/805#discussion_r1919498405
Bug: 396176047
Change-Id: Ia310e0c254ad90967b4e3577e54498fa28532f84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773953
Commit-Queue: ningxin hu <ningxin.hu@intel.com>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491196}
Remove redundant parameters from SendMouseWheelEvent [12/n]
This CL is a part of a series of CLs to refactor how motion events are
handled in `ContentUiEventHandler`.
This CL removes redundant `x`, `y`, `ticks_x`, and `ticks_y`
parameters from `SendMouseWheelEvent` and its JNI wrapper. The values
are now obtained from the `MotionEventAndroid` object.
Bug: 417078839
Change-Id: Ieec0ca978ea58154c0d026cb43324ee262038fa1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6736131
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Keigo Oka <oka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491195}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753306862-6789fc95071645358839e74ba56025cb768385cd-5fe745a715b290c05cc40c3eb6590a904304b147.profdata to chrome-android64-main-1753311747-b7db342dc73c8647d1539bd995ff39bbc6b6f6ff-3667e2e53a3cce646f3710a8408aed305c3892ea.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-android-arm64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Icd29f987a4448a93dca364f4fe1236eec39d65fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782127
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491194}
[pus] plumb the pause_js setting to the renderer side
Mainline-3
For prerendering pages that are triggered by "prerender_until_script"
action, they should pause the JS execution until activation (for MVP).
This CL plumbs this setting from the browser side to the renderer side.
Bug: 428500219
Change-Id: Iae58b7ad503827f75b9f57e021e086baff5b27a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6764926
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491193}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753300775-51765b994e03e6636c589556812c7a4fc8d29a0e-7a00f784447244cdbe8f755ef429c03c5fecd57a.profdata to chrome-mac-arm-main-1753307944-0293fce53192d21b2e00d09c92bd45b280f2cc2c-4c40e1c20da2b4ff6ad23a2da704b7bcbf0acf22.profdata
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-arm-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I05c1671fe036b9b2ec90214afda7129311b2bb10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781989
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491192}
Refactor SendMouseEvent to use MotionEventAndroidSource [11/n]
This change continues the refactoring of the JNI bridge by removing
redundant parameters from the `SendMouseEvent` method. The method now
uses the `MotionEventAndroidSource` to directly access the event data,
simplifying the JNI call and making the code more maintainable.
This is a pure refactoring with no behavior change.
Bug: 417078839
Change-Id: I7491310756f06cf3760c755b6ac8e6bb3d160f9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6736130
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Keigo Oka <oka@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491191}
Roll Enterprise Companion chromium_mac_arm64 from H-lcF-xdzf6ydSO8a... to KYK86AbBYpTxcC8ce...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-mac-arm64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_mac_arm64: https://g-issues.chromium.org/issues/new?component=1604672&template=0
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I81b7e415b6b60040bded4be2e4e6a5e2049fbbf3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781991
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491190}
Roll Enterprise Companion chromium_win_x86_64 from UVrqAtGzmgUEfnEM-... to I9bjoaDlSd9f5OfXj...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-win-x86-64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_win_x86_64: https://g-issues.chromium.org/issues/new?component=1604672&template=0
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: Ibc1738101869446eb5a2a65e3c9ee86352831569
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782014
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491189}
Add trace events to AudioContext, Destination, and SilentSinkSuspender
The following events are added:
- AudioContext::StartRendering()
- AudioContext::StopRendering()
- AudioContext::FrameVisibilityChanged()
- AudioContext::SuspendRendering()
- AudioContext::ResumeOnPrerenderActivation()
- AudioContext::StartContextInterruption()
- AudioContext::EndContextInterruption()
- SilentSinkSuspender::TransitionSinks()
- RealtimeAudioDestinationHandler::SetDetectSilenceIfNecessary()
These events would help to analyze the audio context lifecycle in real
time.
Bug: 415797981
Change-Id: If70ee1f54ff5342dd1ef2d6dca2aa763f6bcd053
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6774346
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491188}
Roll Enterprise Companion chromium_win_x86 from S5floWfqKlbbmjco5... to Ug5VZgL4SCG86isJQ...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-win-x86-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_win_x86: https://g-issues.chromium.org/issues/new?component=1604672&template=0
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I8d274964b046143bdbfac0343d00b8ab47e208a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782015
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491187}
crypto: deduplicate EVPMDForHashKind
This function has 3 copies in //crypto already and several elsewhere in
the codebase. This change moves it onto the crypto/hash interface and
has the other clients in //crypto call that.
Fixed: 430635196
Change-Id: Icfdf3edd365690af63afa72d586bb36d54b1767a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778234
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491186}
Roll clank/internal/apps from a1044967c2ce to 08f659e4dc8f (1 revision)
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/a1044967c2ce..08f659e4dc8f
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll
Please CC agrieve@google.com,chrome-brapp-engprod@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Bug: None
Tbr: agrieve@google.com
No-Try: true
Change-Id: I110b388345832c2f5c0fb684405db1bc942da04a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782145
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491185}
Writing Assistance APIs: Add language expansion feature flags
Add Writer/Rewriter supported language utils, params, flags.
Facilitates experimentation with expanded API language options.
See crrev.com/c/6778695 for plumbing API options to protos.
Bug: 428229777
Change-Id: Id74f644f4160bec49f62262124a30c7610680e5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779232
Commit-Queue: Mike Wasserman <msw@chromium.org>
Auto-Submit: Mike Wasserman <msw@chromium.org>
Reviewed-by: Brad Triebwasser <btriebw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491184}
crypto: get rid of RSAPrivateKey::CreateFromKey
The only remaining clients of it were some net unit tests which already
had an EVP_PKEY in hand, so just use the EVP_PKEYs directly for now.
Bug: 425863216
Change-Id: I00672a691f58198da75bfb85111a674b53bc196e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782099
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491183}
ash: extend the expiry date for the metrics that my team owns.
Set all relevant metrics to be the same expiry date so that it's easier
to extend them in the future.
421901535, 421901635, 418771728, 418772389
Fixed: 400444371, 404246764, 418772233, 417216861, 421901474, 421901438,
Change-Id: Ie47bdc88b46e07ba9d34119e4a1f2ab52e6a5e86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6730500
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491182}
Roll Enterprise Companion chromium_linux64 from R95qtSy1rOs0TjSjv... to ZwB7j920SYwARGX8j...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-linux64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_linux64: https://g-issues.chromium.org/issues/new?component=1604672&template=0
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I3ea1525ea8fa3199ff5420c483c578da18227f65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782012
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491181}
[WebNN] Implement gru and gruCell operations for ORT backend
Bug: 432377532
Change-Id: I909fedf8c3500add63cd04c02b25772554cee6fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6769125
Reviewed-by: Phillis Tang <phillis@chromium.org>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Commit-Queue: Bin Miao <bin.miao@intel.com>
Cr-Commit-Position: refs/heads/main@{#1491180}
Roll Enterprise Companion chromium_mac_amd64 from dlKk0is7o_-2KJCYJ... to fB6AH_X51yaYucp26...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-mac-amd64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_mac_amd64: https://g-issues.chromium.org/issues/new?component=1604672&template=0
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chromium.try:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: Ibaf91371b540d4fdf61c8a3173a16cc0e1edaff1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782013
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491179}
[Read aloud] Use the highlight menu without phrase highlighting.
Previously, the highlight menu [1] was planned to be launched with
phrase highlighting, so the menu was guarded around the phrase
highlighting flag.
However, there's value in launching the menu separate from phrase
highlighting, so this change shows the menu without the phrase
highlighting option by default.
[1] https://screenshot.googleplex.com/9scCCzU8qh47etW.png
Fixed: 428973725
Change-Id: Ieb42b911d0571ff22571ff1e96a7c355d03f0f90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781370
Reviewed-by: Jocelyn Tran <jocelyntran@google.com>
Commit-Queue: Lauren Winston <lwinston@google.com>
Cr-Commit-Position: refs/heads/main@{#1491178}