- Nov 13, 2024
-
-
Alexandros Frantzis authored
If we can't find a dedicated render node check if a card node can be used instead.
-
Alexandros Frantzis authored
Some drivers don't support EGL_DEFAULT_DISPLAY, so use an explicit fallback wl_display object.
-
Alexandros Frantzis authored
This avoid conflicts with native EGL/GL libraries that assume that the libEGL.so, libGLESv2.so ... sonames (used by default for ANGLE) belong to the native EGL/GL implementation and try to query them for specific symbols. This change requires a build with the following GN arg: angle_libs_suffix = "_angle"
-
- Nov 07, 2024
-
-
Emily Shack authored
Bug: 369638286 Change-Id: Ia3298c8acb8948bf1c6a6388e6e56b584f22b690 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001017 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: David Pennington <dpenning@chromium.org> Commit-Queue: Emily Shack <emshack@chromium.org> Auto-Submit: Emily Shack <emshack@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379738}
-
chromium-autoroll authored
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1730981081-0004f13f60ef824293542f474c3f8d00312598c8-2a19011f.profdata to chrome-android64-main-1730990791-b78e9fbabcc43ab34a72a52847cf47790f8b379e-be3589e8.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 Change-Id: I80e933650ed853c867c2527a7a6f3fa388d8f206 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001630 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@{#1379737}
-
This reverts commit 9bd85f44. Reason for revert: LUCI Bisection has identified this change as the culprit of a build failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/compile-analysis/b/8731914295759642129 Sample failed build: https://ci.chromium.org/b/8731914295759642129 If this is a false positive, please report it at http://b.corp.google.com/createIssue?component=1199205&description=Analysis%3A+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F5953705&format=PLAIN&priority=P3&title=Wrongly+blamed+https%3A%2F%2Fci.chromium.org%2Fui%2Fp%2Fchromium%2Fbisection%2Fcompile-analysis%2Fb%2F8731914295759642129&type=BUG Original change's description: > View transition layered capture: determine geometry based on box model > > Instead of capturing the border offset, we capture the following > layout sizes to determine sizing, in addition to the border box: > - padding box > - content box > - The box-sizing property > > - In layered capture mode, we use the content box size as the > reference box for positioning the snapshot, so that padding take > effect. > - The ::view-transition-image-pair pseudo-element now has > position:relative so that it gets affected by padding. It has the > content box size. > - The width/height of the group is determined by the box-sizing > property, and it receives the computed padding. > > Bug: 375395117 > Change-Id: I18fe5126fbfac58b0619043cc5521ea1f280e457 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953705 > Reviewed-by: Khushal Sagar <khushalsagar@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> > Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1379706} > Bug: 375395117 Change-Id: Ibb2eedd23b1010eb909a97589629905971c473fa No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001797 Commit-Queue: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Bot-Commit: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Owners-Override: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1379736}
-
Noémie St-Onge authored
This CL moves the InstructionView to ios/chrome/common so that it can be used in the CPE. The `InstructionViewRowAccessibilityIdentifier` helper method also had to be moved to remove all ios/chrome/browser dependencies. CL using the InstructionView in the CPE: crrev.com/c/5995410. Bug: 355042392 Change-Id: I316b9b83f9389186dcd5a6cead92c5a88519108e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5990012 Reviewed-by: Rohit Rao <rohitrao@chromium.org> Commit-Queue: Noémie St-Onge <noemies@google.com> Cr-Commit-Position: refs/heads/main@{#1379735}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libc.git/+log/194ae301adda..32df7a8cf5cd 2024-11-06 51221277+SoftJing1@users.noreply.github.com [libc] add mremap (#112804) 2024-11-06 duncpro@icloud.com [libc] [unistd] implement pipe2 syscall wrapper (#114474) 2024-11-05 michaelrj@google.com [libc] Fix sendmsg iovec unpoisoning (#115057) 2024-11-05 michaelrj@google.com [libc][NFC] Correct test header inclusion, license (#114604) 2024-11-05 its.overmighty@gmail.com [libc][newhdrgen] Fix NameError in yaml_to_classes.py (#114952) 2024-11-04 huberjn@outlook.com [libc] Disable failing AMDGPU test temporarily 2024-11-04 mcgrathr@google.com [libc] Define away __restrict in C++ without GNU extensions (#114655) 2024-11-03 jobhdezlara93@gmail.com [libc] Fix typos in proxy type headers (#114717) 2024-11-03 jobhdezlara93@gmail.com [libc] add stdlib.h header to the _Exit func proxy in full build (#114718) 2024-11-03 jobhdezlara93@gmail.com [libc] Add proxy headers to handle memory allocation associated with the header `#include <stdlib.h> (#114690) 2024-11-03 shouryagoel10000@gmail.com Comment out CF16 entrypoints for aarch64 and CF128 entrypoints for X84-64 (#114696) 2024-11-03 shouryagoel10000@gmail.com [libc][complex] implement different flavors of `creal` and `cimag` functions (#113300) 2024-11-02 jobhdezlara93@gmail.com [libc] Remove the #include <stdlib.h> header (#114453) 2024-11-01 nickdesaulniers@users.noreply.github.com [libc] disable failing include tests (#114619) 2024-11-01 nickdesaulniers@users.noreply.github.com [libc][cmake] disable include tests in overlay mode (#114566) 2024-11-01 oleksandr.tarasiuk@outlook.com [libc] rename LLVM_LIBC_SRC___SUPPORT_UINT_H to LLVM_LIBC_SRC___SUPPORT_BIG_INT_H for consistent naming (#114592) 2024-11-01 lntue@google.com [libc] Use relative inclusion for public headers. (#114324) 2024-11-01 c8ef@outlook.com [NFC] Simple typo correction. (#114548) 2024-11-01 nickdesaulniers@users.noreply.github.com [libc][cmake] make i386 distinct from x86_64 (#114477) 2024-11-01 lntue@google.com [libc] Remove FE_ALL_EXCEPT check in hdr/fenv_macros.h. (#114446) 2024-10-31 michaelrj@google.com [libc] Remove asm-generic includes from tests (#114479) 2024-10-31 michaelrj@google.com [libc] Fix macro definition hermeticity (#114467) 2024-10-31 michaelrj@google.com [libc] Fix path to fcntl_overlay in cmake (#114464) 2024-10-31 nickdesaulniers@users.noreply.github.com [libc][i386] syscall support (#114264) 2024-10-31 lntue@google.com [libc] Fix memory leak in MPFRWrapper cospif with MPFR pre 4.2. (#114415) 2024-10-30 lntue@google.com [libc] Fix usage of std::nullptr_t in LibcTest.h. (#114321) 2024-10-30 george.burgess.iv@gmail.com [libc] fix behavior of strrchr(x, '\0') (#112620) 2024-10-30 michaelrj@google.com [libc] Refactor statvfs tests (#114147) 2024-10-30 nickdesaulniers@users.noreply.github.com [libc][i386] setjmp/longjmp (#112437) 2024-10-30 george.burgess.iv@gmail.com libc: strlcpy/strlcat shouldn't bzero the rest of `buf` (#114259) 2024-10-30 nickdesaulniers@users.noreply.github.com [libc][i386] define MINSIGSTKSZ & SIGSTKSZ (#114249) 2024-10-30 mcgrathr@google.com [libc] Fix fexcept_t type to match canonical ABI and API (#113666) 2024-10-29 vonosmas@gmail.com Remove spurious includes from sinpif_test.cpp 2024-10-29 wldfngrs@gmail.com [libc][math][c23] Add cospif16 function (#113001) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/llvm-libc-chromium Please CC ayzhao@google.com,lexan@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: ayzhao@google.com Change-Id: I23770184daff166d8f062c0d967220bb07ea9c16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001871 Commit-Queue: Eric Boren <borenet@google.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by: Alan Zhao <ayzhao@google.com> Cr-Commit-Position: refs/heads/main@{#1379734}
-
chromium-autoroll authored
https://chromium.googlesource.com/crossbench.git/+log/20bc63300a82..17b0a7e691e9 2024-11-07 victorvianna@google.com Move CPUFrequencyMapTestCase to different file If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/crossbench-chromium Please CC cbruni@google.com,crossbench@chromium.org,khokhlov@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: khokhlov@google.com Change-Id: Ia953a82d811cdbe618115b7e0b23c5684189bbe2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003262 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@{#1379733}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/ios_internal.git/+log/7360207dbf40..22d70c300a91 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/ios-internal-chromium-autoroll Please CC chrome-brapp-engprod@google.com,sdefresne@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 Change-Id: I72acdbd33d0693e64222ace749edeed9cd550069 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6002030 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@{#1379732}
-
Olivier ROBIN authored
SessionSyncService::GetOpenTabsUIDelegate can return null [1], so handle this case. [1]: https://source.chromium.org/chromium/chromium/src/+/main:components/sync_sessions/session_sync_bridge.cc;l=125 Bug: 377703254 Change-Id: I0538601cccdcba45feabb8604e885a33c52e08f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003008 Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379731}
-
Ernesto Izquierdo Clua authored
This patch adds support of xframe form submissions detected in the page content world. For this, child frame tokens generated in the isolated world are made available to the page content world by storing them in the DOM. The page content world script that handles form submissions now sends the browser the child frame tokens as part of the form submission event metadata. Fixed: 372688163 Change-Id: I07678b8b97499d48c1a185f111f3b9e0505af009 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6000833 Reviewed-by: Vincent Boisselle <vincb@google.com> Commit-Queue: Ernesto Izquierdo Clua <eic@google.com> Cr-Commit-Position: refs/heads/main@{#1379730}
-
Jeongwoo Park authored
Change-Id: Idfe7c2ed51b7aa42082863f07383ec17acd3a0d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5974388 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379729}
-
Maksim Sadym authored
Bug: 42323268 Change-Id: I69816c73d9985e7e20a6205ba08ef68c946467f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999310 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Maksim Sadym <sadym@chromium.org> Reviewed-by: Vladimir Nechaev <nechaev@chromium.org> Reviewed-by: Maksim Sadym <sadym@chromium.org> Auto-Submit: Nikolay Vitkov <nvitkov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379728}
-
Benjamin Williams authored
This CL updates the display logic for Tips-related ephemeral modules to consider the existing kIsNewUser signal when evaluating eligibility. This change aims to avoid overwhelming new users with multiple modules and potential conflicts with the Set Up List module. The updated logic ensures that Tips ephemeral modules are suppressed for new users, providing a more streamlined onboarding experience. Change-Id: I7e1a5bc015ac629fc2321fd93fa7fd45f72403a5 Fixed: 377728768 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6000683 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Auto-Submit: Benjamin Williams <bwwilliams@google.com> Reviewed-by: Chris Lu <thegreenfrog@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379727}
-
Alex Rudenko authored
Fixed: 40822374 Change-Id: I1dc07faeab2d7e09c5c163244d9ab14bdb59c646 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999393 Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379726}
-
Dan Polanco authored
This CL is part of a 3-sided patch to update the content description of the Bottom Sheet. It removes the temporary defaults and the old header method in the BottomSheetContent.java file. Bug: 350775184 Change-Id: I310396879b419f744a1ff7132618b7408b15ec57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003182 Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org> Commit-Queue: Dan Polanco <polardz@google.com> Reviewed-by: Theresa Sullivan <twellington@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379725}
-
Colin Blundell authored
My experience with //gpu extends beyond SharedImage at this point :). Change-Id: Id007507c27cc12ee0a46f8280a8811be4c625a12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999983 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379724}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/e9f78daf355e..1598fc5112c4 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 chrome-brapp-engprod@google.com,kraskevich@google.com,mdjones@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: kraskevich@google.com,mdjones@google.com No-Try: true Change-Id: I638462f8f5be430541adbd5e794d6eae3b3cd2db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003284 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@{#1379723}
-
David Bienvenu authored
Add a comment to windows_h_disallowed.h to give a quick way to find the include path for a disallowed include of Windows.h. Also add an include of windows_h_disallowed.h to content/browser/devtools/protocol/webauthn_handler.cc to give a more useful message than obscure errors about GetUserNameW if Windows.h is included. Bug: 40555612 Change-Id: I4dd948dc9ece10e695fce405ace87c0425724935 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5988431 Reviewed-by: Jesse McKenna <jessemckenna@google.com> Commit-Queue: David Bienvenu <davidbienvenu@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379722}
-
Chrome Release Bot (LUCI) authored
* This is an automated release commit. * Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true Change-Id: Ie3554da18e5cbb65560ca59e75cc87fe64f880df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003283 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1379721}
-
Andreu Botella authored
When `text-box-trim: trim-end` is used together with `line-clamp`, it should trim the block-end leading of the last line before clamp, the one with the ellipsis. This worked when that last line before clamp is directly contained by the line-clamp container, but it doesn't when it is inside a nested block element. The reason for this is that, although for `InlineNode`s, `ConstraintSpace::ShouldTextBoxTrimNodeEnd` is always set if the parent `BlockNode` is as well; for `BlockNode`s, that flag is only set for nodes that are the last in-flow child node of its parent. This means that, for line-clamp, there is no flag to tell a child `BlockNode` that it is fine to trim if there's a clamp point inside it, even if it wouldn't be fine to trim in its last formatted line. This patch therefore adds a `ShouldTextBoxTrimInsideWhenLineClamp` field to `ConstraintSpace` to indicate this. Bug: 40336192, 40254880 Change-Id: I1690ab296dd9686a09f4b9f06a7d86d8998d9446 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5987915 Commit-Queue: Andreu Botella <abotella@igalia.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379720}
-
Jihad Hanna authored
It makes more sense for such a util function to exist in the header. Low-Coverage-Reason: TRIVIAL_CHANGE This CL only moves code. Bug: 40100455 Change-Id: I3e29d2efa2c644a840dceb10ebe00ae48515be4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5993439 Reviewed-by: Florian Leimgruber <fleimgruber@google.com> Commit-Queue: Jihad Hanna <jihadghanna@google.com> Cr-Commit-Position: refs/heads/main@{#1379719}
-
Xiaochen Zhou authored
network is revoked. Fenced frames(FF) can disable network access by invoking FF API: window.fence.disableUntrustedNetwork(). After the network access is revoked, FF will get access to cross-site data, for example, via shared storage get API. The principle is no network request can be made using URLs in a network-disabled FF, including user triggered main-frame navigations. This is because the URL can leak cross-site data, for example, by appending the cross-site data to the URL. This CL disables Open Link in Web App context menu options when FF network is revoked. Bug: 364906216 Change-Id: I9f7f2b64490a0b3c7d393fd386b1cca36a99919e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5939360 Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Commit-Queue: Xiaochen Zhou <xiaochenzh@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379718}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202411070600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/XO2q38wA0_WaN_NDOlmpuy-764LyBMLBLzD_mSPyt_MC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC cros-essential-apps-dev@chromium.org,jomag@google.com,media-app@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://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:chromeos-betty-chrome;luci.chrome.try:linux-chromeos-chrome Bug: b/357143265,b/365543624,b/375276569 Tbr: media-app@grotations.appspotmail.com Change-Id: I6308e9f4535ffa0b36981d92f251a11a91ce8f6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6002856 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@{#1379717}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/a5676c17b393..7589689774d2 2024-11-07 eshr@google.com Replace cricket::LeastCommonMultiple and cricket::GreatestCommonDivisor with std::lcm and std::gcd. 2024-11-07 eshr@google.com SEA discards inactive encoders in implementation name If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com,webrtc-infra@google.com on the revert to ensure that a human is aware of the problem. To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/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: webrtc-chromium-sheriffs-robots@google.com Change-Id: Id67f23fe88b521da4ecae284edaf9866ad44334e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003242 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@{#1379716}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/9d9a94ce6947..e9e132590a7c 2024-11-07 ddiproietto@google.com Merge "Fix build with bazel 7.3" into main 2024-11-07 ddiproietto@google.com Merge "Disable JIT for debuggable test app" into main If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com,primiano@chromium.org 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:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I37535c92d7418157a86c209052d1b6807d6bdd78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6002028 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@{#1379715}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/devtools/devtools-internal.git/+log/959629b200a9..38b9a7667609 Also rolling transitive DEPS: https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/49a007dcfe1def81ca90bc592b3cb178da2fa3ac..69a4b1e6e8594204773d99e26a1e3ff5e3e3a9c5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/devtools-internal-chromium Please CC devtools-waterfall-sheriff-onduty@rotations.google.com,liviurau@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: devtools-waterfall-sheriff-onduty@rotations.google.com Change-Id: I8e16b8e5c18531d41be2c6e610f3b0a7c733b927 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6002026 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@{#1379714}
-
LK Kupoluyi authored
Bug: 376274500 Change-Id: I1fe10f58c3cb6bb50dae8e7359154c6ee06046d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5980293 Reviewed-by: Evan Liu <evliu@google.com> Reviewed-by: Akihiro Ota <akihiroota@chromium.org> Commit-Queue: Jesulayomi Kupoluyi <lkupo@google.com> Cr-Commit-Position: refs/heads/main@{#1379713}
-
Jihad Hanna authored
Bug: 40227071 Change-Id: I43a93c382949fdf9bb64e680c8c8f5fd25d46cf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5993756 Reviewed-by: Florian Leimgruber <fleimgruber@google.com> Commit-Queue: Jihad Hanna <jihadghanna@google.com> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1379712}
-
chromium-internal-autoroll authored
Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202411070600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/jFIIGvVNtQb50xZwMNjSkZdwT1w_-9FIegJrf4j-gFwC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC cros-essential-apps-dev@chromium.org,help-app@grotations.appspotmail.com,jomag@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/372362266,b/376842380,b/377532955 Tbr: help-app@grotations.appspotmail.com Change-Id: I1118c0505810921b5adcb9d730e3329c0e43e05a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003085 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@{#1379711}
-
Alex Rudenko authored
Fixed: 40206207 Change-Id: I9f647a5ba7fcf47ee435927a8f3c87d7691175fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999743 Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379710}
-
Keishi Hattori authored
Change-Id: I33919e572396fb32d37626121647fe3ed097d05e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999855 Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by: Takashi Sakamoto <tasak@google.com> Cr-Commit-Position: refs/heads/main@{#1379709}
-
gaiko authored
Set scroll state to fetch from active scrolling tracker when making pipeline reporters for backfilled frames. Presented frame pr: https://screenshot.googleplex.com/AAds6BJNYfCHPtX Backfill pr: https://screenshot.googleplex.com/6iwvCBgqPhAuhNb Bug: 40213368 Change-Id: Ic3f0ff90d564b6d640a7440ce6999856a135e9ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5952948 Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Commit-Queue: Stacy Gaikovaia <gaiko@google.com> Auto-Submit: Stacy Gaikovaia <gaiko@google.com> Cr-Commit-Position: refs/heads/main@{#1379708}
-
Din Nezametdinov authored
Currently, desktop manual password generation is available on a field in the following cases: 1) The field has type="password". 2) The field was type="password" field at some point of time. 3) The field has a variation of the word "password" in name/id attributes. 4) The server predicts the field as new password field. This CL replicates the same logic for android. Tested on https://shaihitdin.github.io/input_type_text_name_password/ 1) Manual password generation is working on the text field. 2) Manual filling is unavailable on the text field. Bug: 356817239, 372635030 Validate-Test-Flakiness: skip Change-Id: If3b2fc8fd23ee699a610def9358fcba35f56e5ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5947566 Reviewed-by: Ioana Pandele <ioanap@chromium.org> Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Din Nezametdinov <shaikhitdin@google.com> Cr-Commit-Position: refs/heads/main@{#1379707}
-
Noam Rosenthal authored
Instead of capturing the border offset, we capture the following layout sizes to determine sizing, in addition to the border box: - padding box - content box - The box-sizing property - In layered capture mode, we use the content box size as the reference box for positioning the snapshot, so that padding take effect. - The ::view-transition-image-pair pseudo-element now has position:relative so that it gets affected by padding. It has the content box size. - The width/height of the group is determined by the box-sizing property, and it receives the computed padding. Bug: 375395117 Change-Id: I18fe5126fbfac58b0619043cc5521ea1f280e457 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953705 Reviewed-by: Khushal Sagar <khushalsagar@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379706}
-
Simon Ziegltrum authored
Bug: 327270907 Change-Id: I27c313f64084c238b2d5aabf84d0f29f66f81c72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999494 Reviewed-by: Osama Fathy <osamafathy@google.com> Commit-Queue: Osama Fathy <osamafathy@google.com> Auto-Submit: Simon Ziegltrum <ziegltrum@google.com> Cr-Commit-Position: refs/heads/main@{#1379705}
-
Morten Stenshorne authored
Was only enabled in a browsertest. Bug: 356235816 Change-Id: I672c39e3285e4a740cdd40d9dbe418a0f262bd71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999959 Reviewed-by: Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379704}
-
Filipa Senra authored
This CL records the time range user actions ClearBrowsingData_* for QD. These are usually recorded in the BrowsingDataRemover. However, QD doesn't trigger the removal with a timerange but with timestamps. As such, no user action for the time range is recorded. Bug: 335387869 Change-Id: Ie0f848484b1f2d845e1c94f47fb4f38b0bb951ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001957 Reviewed-by: Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Filipa Senra <fsenra@google.com> Cr-Commit-Position: refs/heads/main@{#1379703}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/082cc384c491..9d9a94ce6947 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 chrometto-team@google.com,perfetto-bugs@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: perfetto-bugs@google.com Change-Id: I4d2b1da83dc2cd1a686cc361740373e1c3be0156 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6003204 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@{#1379702}
-