- 10 Nov, 2020 40 commits
-
-
Brian Geffon authored
Node channel messages need to be packed. Bug: b:172869067 Change-Id: I30ac9d44347fef9e0b74267d6d09ec8589e4d3e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527532Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Brian Geffon <bgeffon@chromium.org> Cr-Commit-Position: refs/heads/master@{#825686}
-
Yu Su authored
- Add a ChipRenderParams class to wrap the params used when displaying the chip - add new LensController methods to retrieve chip params, generate Lens intent and launch Lens. Will implement these methods in a follow up clank cl. - update LensQueryParams to be a temperate wrapper object for Lens init params. Will split out Lens init params into a separate wrapper object once we have the Direct intent SDK. Change-Id: If90ac5f407889069fe2f58ef210055d2c144df46 Bug: 1145748, b/171252338 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527724 Commit-Queue: Yu Su <yusuyoutube@google.com> Reviewed-by:
Ben Goldberger <benwgold@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#825685}
-
Mark Mentovai authored
In a change from x86_64, macOS on arm64 requires MAP_JIT for code not using the hardened runtime. However, if MAP_JIT is specified for signed code lacking the JIT entitlement, mmap and mprotect fail with EINVAL, so it’s still not possible to use MAP_JIT everywhere it could conceivably be required. A wasm attempt to mprotect a region as PROT_READ | PROT_WRITE | PROT_EXEC was succeeding in signed builds but failing in non-hardened-runtime processes with EPERM as a result of the mapping lacking MAP_JIT. In a previous (post-facto drive-by) review of this code (https://chromium-review.googlesource.com/c/2078792), I noted “I would have preferred the caller coming in with affirmative knowledge of whether it wanted JIT or not” but the callers aren’t necessarily aware of the entitlement regime they’re expected to run under. Bug: 1144200 Change-Id: I2edde64922dfbd8ba7158cc741b0e82d680235b8 CQ-Include-Trybots: luci.chromium.try:mac-arm64-rel Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523446Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Mark Mentovai <mark@chromium.org> Cr-Commit-Position: refs/heads/master@{#825684}
-
Alex Moshchuk authored
This modifies an existing test, DynamicIsolatedOriginTest.NewBrowsingInstanceInOldProcess, to explicitly exercise a scenario where a process's minimum BrowsingInstance ID changes, and where this may affect a CanAccessDataForOrigin decision. In particular, this would happen if the new minimum BrowsingInstance ID makes a particular origin eligible for isolation. Currently, the minimum BrowsingInstance ID stored for a process in ChildProcessSecurityPolicy does not change even if the corresponding BrowsingInstance goes away, so the outcome of CanAccessDataForOrigin can't change. This will change once multiple BrowsingInstances are tracked for each process, rather than just a minimum ID, in issue 1135539. In particular, after this change, CanAccessDataForOrigin may start denying access to an origin which is considered isolated in all of the process's remaining BrowsingInstances, due to citadel enforcement. Bug: 1135539 Change-Id: I8d388f6099f224172b8a77129362de8300e37ecc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528128Reviewed-by:
Charlie Reis <creis@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#825683}
-
Curt Clemens authored
E.g. var(--google-gray-refresh-700). The values on all of the pages outside of settings had hard-coded colors. Change-Id: Idefc2c9746f13f02521712a2e7740eaaca97b62f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523662 Commit-Queue: Curt Clemens <cclem@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#825682}
-
Maggie Chen authored
It's split into AddSurfaceDamageToDamageList(), AddRenderPassFilterDamageToDamageList() and FindQuadWithOverlayDamage() for better readability. These new functions are called based on the following. AddSurfaceDamageToDamageList() is called per surface, form CopyPasses(), HandleSurfaceQuad() and EmitSurfaceContent(). AddRenderPassFilterDamageToDamageList() is called per render pass, from CopyQuadsToPass(). FindQuadWithOverlayDamage() is called from CopyQuadsToPass() where we set the |overlay_damage_index| in shared_quad_state. Bug: 1117235 Change-Id: Ibbd2ada71cc0fc0deaaed1b7da1c475d35f910f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2493836 Commit-Queue: Maggie Chen <magchen@chromium.org> Reviewed-by:
weiliangc <weiliangc@chromium.org> Cr-Commit-Position: refs/heads/master@{#825681}
-
Kent Tamura authored
* Use RenderingTest::GetLayoutBoxByElementId() to reduce the usage of ToLayoutBox(). * Use Element::GetLayoutBox() instead of Element::GetLayoutObject() to reduce the usage of ToLayoutBox(). This CL has no behavior changes. Bug: 891908 Change-Id: I5d18e3ff061d0d4b7953fbfb21c0d314bf78a776 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526665 Commit-Queue: Koji Ishii <kojii@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#825680}
-
Noel Gordon authored
The PageHandler and UI components can depend on each other, which is a subject of an upcoming CL. This CL to avoid the `gn check` errors that would result with separate build rules for these items in that upcoming CL. Preparatory patch. No change in behavior. Bug: 1113981 Tbr: alex Change-Id: Ifeb988d1ce11e548bcb2b2d56021f2d89d8be526 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528514Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#825679}
-
danielng authored
Adding metrics that will be used to record information about the borealis installation flow. These will be used to help measure the performance, usage and reliability of the installer. Cq-Depend: 2509072 Bug: b/171758529 Change-Id: I4c078f388ba67cf858cacea78b102211d003edba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515863 Commit-Queue: Daniel Ng <danielng@google.com> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Nic Hollingum <hollingum@google.com> Cr-Commit-Position: refs/heads/master@{#825678}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Iac1af4c9052003030bb23e54b25ea3afa443728b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528714Reviewed-by:
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/master@{#825677}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/59992a0fea40..c32d29e103de 2020-11-09 jalyn@microsoft.com Update KeyboardShortcutAction enum to match browser If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1140386,chromium:174309 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ieea34c21c7d2dbdd00ea56c1b1ee96f0a5bde0d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527798Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-aemu-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I169467009bc38ede203b8b654528f321dc815105 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528715Reviewed-by:
-
Carlos Frias authored
Enable Sensors control policies for launch in M88: DefaultSensorsSetting SensorsAllowedForUrls SensorsBlockedForUrls Bug: 1108589 Change-Id: I9d643a4a6edb0264341d34e3358c8e1be35440eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362999 Commit-Queue: Carlos Frias <carlos.frias@microsoft.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#825674}
-
mlcui authored
- Update JSDoc type of uiLanguage to include the missing undefined - Fix exceptions if uiLanguage is undefined (doesn't happen in practice) - Add missing dependencies to the computed binding - Prevent extra comma from appearing if input method is not found Bug: None Change-Id: I5bc3dc3849bbb29e92c4a636c511dba69b60aa3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2525562Reviewed-by:
My Nguyen <myy@chromium.org> Commit-Queue: Michael Cui <mlcui@google.com> Cr-Commit-Position: refs/heads/master@{#825673}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/9b7f81867ddd..1d532cbd0baa If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I1cc15bba26848b99a0faaf457b55ae1b3f602e58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528713Reviewed-by:
-
Noel Gordon authored
Add fakes of the API calls file manager makes to its chrome background extension page. Add a TODO to rename this file. These fakes are copied from their externs file definitions [1]. Also includes fakes for window.metrics, and chrome.{storage,extension} until we find a better home for them. Taken together, these are the minimum number of fakes needed to render current files app code in the SWA container. [1] https://bit.ly/3n9Ckbv chrome/src/ui/file_manager/externs Bug: 1113981 Change-Id: Ic53fe5f50f2fd97a557292fc308c0d7dd16004bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528513 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Auto-Submit: Noel Gordon <noel@chromium.org> Reviewed-by: -
Wenbin Zhang authored
We only have 4 bots on win7-perf and there's no backup for those old models. Now we are only running a small set of tests on win 7, we can reduce the shard count to 3 to avoid capacity issue. Bug: chromium:1146593 Change-Id: I05187c0b65742cd9f06d12ee1e180065a548f30b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2525860Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Wenbin Zhang <wenbinzhang@google.com> Cr-Commit-Position: refs/heads/master@{#825670}
-
Nnamdi Theodore Johnson-Kanu authored
Bug: 093185 Change-Id: Ic66508d92a5eb9c0d72c4b21e7517cbabb4563d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507295 Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com> Reviewed-by:
-
Moe Ahmadi authored
Modules wait for the promo to be loaded before showing. The promo is considered loaded when the ntp-middle-slot-promo has been fired by the promo element. This event is expected to be fired whether or not there is a promo data available. crrev.com/c/2505739 changed that behavior causing NTP Modules to remain hidden when there is no promo data. Fixed: 1147257, 1143366 Change-Id: If0c14ec8ee142fd38cdbc1bf9249f3345db6ca82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527854 Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Auto-Submit: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#825668}
-
Charlene Yan authored
Bug: 1116118 Change-Id: I1d187df059f74e9e08fa2b55aedb29b86e29693d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523470Reviewed-by:
Taylor Bergquist <tbergquist@chromium.org> Commit-Queue: Charlene Yan <cyan@chromium.org> Cr-Commit-Position: refs/heads/master@{#825667}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b5e18417..0833ef41 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I50f4182d502006d0c53fb1563c64d672096b7ff9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527347Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#825666}
-
Brian Liu Xu authored
Do not process window management mouse messages (WMMMs) when the pen is active over the client area. Windows sends window management mouse messages at the mouse position when windows open or close (e.g. Aura tooltips and Status Bubbles), including WM_MOUSEMOVE, WM_NCMOUSEMOVE, and WM_SETCURSOR. This is a longstanding Windows behavior designed to ensure that mouse cursor visuals and hover states update when the foreground window changes. However, this behavior does not extend to pen input, so WMMMs always come with the mouse coordinates instead of with the pen coordinates even if there is an active pen. In Chromium, WM_POINTER processing in the window non-client area are "promoted" to mouse messages in order to allow for interaction with the native window frame (e.g. resize handles, title bar, and window caption buttons). However, WM_POINTER messages in the window client area are handled as Chromium events without any mouse promotion; in this latter case, mouse position and pen position are not guaranteed to be in sync. Since Aura tooltips and Status Bubbles appear as custom windows on pen hover, opening/closing them causes Windows to send WMMMs. Consequently, users might see visual flickering as hover states flip back and forth between pen and mouse positions. In order to ensure that these WMMMs do not interfere with hover states, we must ignore such messages until the pen is no longer active. This change affects only Windows 8 and newer clients, which use the WM_POINTER API. Bug: 1147222 Change-Id: I44335348f933f48edcfe665b396f133388169957 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2525220 Commit-Queue: Brian Liu Xu <brx@microsoft.com> Auto-Submit: Brian Liu Xu <brx@microsoft.com> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#825665}
-
Mark Pearson authored
It's flaky. TBR=rbpotter@chromium.org BUG=1147205 Change-Id: I8461641ba7380178e272e7a6ab1908de50f9b1c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527672Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#825664}
-
Noel Gordon authored
Change chrome_file_manager_private_test_impl.js so that it can be used in files SWA. No change in behavior. When the code is used in SWA, simulate test.Event because code further down in this chrome.fileManagerPrivate mock expects it to exist. This code is also used by the file manager UITests and that code needs a MockVolumeManager so we must create one in the UITests case. Test: browser_tests --gtest_filter="FileManagerUITest*" Tbr: alex Bug: 1113981 Change-Id: I0adc6c15a9dfaf3ced49dd9ba34a9ed900218dd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526822Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#825663}
-
Josh Karlin authored
Renames the table from sites_blacklist to sites_blocklist. This required bumping the database version up to 3. Modified the test databases to include a row to ensure that it's correctly carried over when migrgated. Bug: 1097286 Change-Id: I96d997377ae854fef23920f5f1b77a6ec773d247 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495696Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Reviewed-by:
Peter Williamson <petewil@chromium.org> Commit-Queue: Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#825662}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1604685414-e1e235adb1c3aa909026ef65a3bd85555a33e659.profdata to chrome-win64-master-1604955437-c91abc52162c185f79a73166dbe14ec0b1c66fea.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 pgo-profile-sheriffs@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Iff180398a0edfadaf5b5d090543dcedbdd218c68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527795Reviewed-by:
-
Xinghui Lu authored
Only users who queried the feature flag are counted as active. Check the feature flag first to make sure there is no difference of group sizes in different experiment groups. There is no behavioral change in this CL. Bug: 1097310 Change-Id: Ib502759bce7d965641f4df49dddfa7b659eab50e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527759 Auto-Submit: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#825660}
-
Fergus Dall authored
Tooling which tries to find the owning component for a file for e.g. automated bug filing seems to only look at the OWNERS files in the direct ancestory of that file, it doesn't look at files included from elsewhere in the tree. Therefore we should add our component to everything to prevent bugs from being lost. Bug: 1113581 Change-Id: I784dd868f54d84cc226883405250c7acaf1c0b29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528516 Commit-Queue: Fergus Dall <sidereal@google.com> Commit-Queue: Daniel Ng <danielng@google.com> Auto-Submit: Fergus Dall <sidereal@google.com> Reviewed-by:
Daniel Ng <danielng@google.com> Cr-Commit-Position: refs/heads/master@{#825659}
-
Jesse Schettler authored
Add a progress bar and use it to display scan progress. Bug: 1059779 Change-Id: I9172be485799002364f4d5259fdbe006e80f6d02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521695 Commit-Queue: Jesse Schettler <jschettler@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Cr-Commit-Position: refs/heads/master@{#825658}
-
Wei Lee authored
Bug: b/172345161 Test: tast run [DUT] camera.CCAUI* Change-Id: I10484c9263f3e4c560028aef272cd3db88c47b31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2509834 Commit-Queue: Wei Lee <wtlee@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Auto-Submit: Wei Lee <wtlee@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#825657}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=benmason@chromium.org Change-Id: I5170fa85640ecf95c26b0f000fdcb6169073ccdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527628Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#825656}
-
Noel Gordon authored
The files app front-end code creates a metadata Shared Worker. Provide a helper routine to do that and document it. Allow the routine to work if window.isSWA is defined [1]. [1] window.isSWA is not defined today, so no change in behavior. Bug: 1113981 Change-Id: Ib42ccadec1ee853758175ff018322954fd42c27c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2526666 Commit-Queue: Noel Gordon <noel@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Auto-Submit: Noel Gordon <noel@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/982b2a757087..e7a31f42cda3 2020-11-10 sokcevic@google.com Support main branch in bot_update If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC sokcevic@google.com,ajp@google.com,apolito@google.com,ehmaldonado@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: sokcevic@google.com,ajp@google.com,apolito@google.com,ehmaldonado@google.com Change-Id: I21dd97b39154aaaf11633c3acb38e121b1f50968 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528709Reviewed-by:
-
Kai Ninomiya authored
Blink must also validate against 0xFFFF'FFFF coming in from JS, to prevent it from being interpreted as WGPU_STRIDE_UNDEFINED by Dawn. Currently this is done as an exception, but later needs to be an error injected into the command encoder. Bug: dawn:520, dawn:566 Change-Id: Ie9c992ffab82830090d0dfc3120731e89cd9691c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2504584Reviewed-by:
Austin Eng <enga@chromium.org> Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#825653}
-
Yulun Wu authored
Bug: 1147178 Change-Id: I0daed330aa98fee3166372f98c693cbef6ab5a69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527843 Commit-Queue: Yulun Wu <yulunwu@chromium.org> Reviewed-by:
-
Jesse Schettler authored
Bug: 1059779 Change-Id: I9005fb60fdff0c38526411125614f6883ea3cbfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527883 Commit-Queue: Jesse Schettler <jschettler@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/9b7f81867ddd..1d532cbd0baa If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Iff99a34ad586a3993c69b8ffee9750db1c8350c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528569Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/489f2c838bb7..528ae31edd58 2020-11-09 jmadill@chromium.org Vulkan: Move ExtensionNameList out of the class. 2020-11-09 jmadill@chromium.org Vulkan: Move primary command buffer to CommandQueue. 2020-11-09 jmadill@chromium.org Traces: Use 4 download threads. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC timvp@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: timvp@google.com Change-Id: I0ee2d7ce821d16dbed062d5dd9f828d0f548aac4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528611Reviewed-by:
-
Nate Chapin authored
Change-Id: I47f74861053c14ddb9cc78ddfd360048968390e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523065 Commit-Queue: Nate Chapin <japhet@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by:
-
Jesse Schettler authored
https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/284391894473..97f865a06daa $ git log 284391894..97f865a06 --date=short --no-merges --format='%ad %ae %s' 2020-11-06 fletcherw lorgnette: add CancelScan constant and permissions 2020-11-01 yichengli cryptohome: Add userdataauth implementation for GetWebAuthnSecret 2020-09-17 yichengli cryptohome: Set up WebAuthn secret during mounting Created with: roll-dep src/third_party/cros_system_api Change-Id: Ie04adba40fc0dbb2ce1b0d8470d7ab3518c881bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527425Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Jesse Schettler <jschettler@chromium.org> Cr-Commit-Position: refs/heads/master@{#825647}
-
