- 08 Jan, 2020 40 commits
-
-
chrome://discardsDan Beam authored
R=chrisha@chromium.org Fixed: 1039223 Change-Id: I314aaaf0682dea7cb962cd247fb1430b4d7e7267 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989980 Auto-Submit: Dan Beam <dbeam@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#729490}
-
Elly Fong-Jones authored
Instead, use the explicit setter on DialogDelegate. Thankfully IDS_APP_CANCEL is already the default for ui::DIALOG_BUTTON_CANCEL :) Bug: 1011446 Change-Id: Ifc67f637732c07137c2b65b54fbba64f2f0c77d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992189Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#729489}
-
Fabrice de Gans-Riberi authored
The test flakes regularly on both debug and release bots. TBR=fdegans@chromium.org Bug: 1040202 Change-Id: I0b6c822351d0646ba748fc1ce4b4809d0b1ac174 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992305Reviewed-by:
Fabrice de Gans-Riberi <fdegans@chromium.org> Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org> Cr-Commit-Position: refs/heads/master@{#729488}
-
Elly Fong-Jones authored
This reverts commit 8b4578d6. Reason for revert: This change breaks running any tests on macOS systems that do *not* already have MAC_CHROMIUM_TMPDIR set; the generated value for it if it is unset is far too long (eg on my system it is "/var/folders/yd/p_tdv3gs24904_gjb44140tc003h8w/T/.org.chromium.Chromium.VHPP1z/0"), which hits the DCHECK here: https://cs.chromium.org/chromium/src/base/files/file_util_mac.mm?type=cs&q=MAC_CHROMIUM_TMPDIR&sq=package:chromium&g=0&l=35 To repro that failure: 1) build at trunk 2) $outdir/browser_tests Original change's description: > Improve temp dir handling for child procs on Windows and macOS. > > Tests may leak files/directories in temp due to ScopedTempDir lifetime > issues (see linked bug) or as a result of crashes. This CL augments the > TestLauncher to handle such leaks a bit better. When launching a child > proc on Windows and macOS, the TestLauncher now directs that child to > its own dedicated temporary directory. Upon child exit, the launcher > checks for leaked files/directories in that dir and deletes the dir. On > test iteration completion, the launcher will emit a list of the tests > that produced leaks when run with --test-launcher-print-temp-leaks that > looks a lot like this: > > ERROR: 2 files and/or directories were left behind in the temporary directory by one or more of these tests: PaymentManagerTest.ClearPaymentInstruments:PermissionControllerImplTest.ResettingOverridesForwardsReset:PermissionControllerImplTest.SettingOverridesForwardsUpdates:PermissionControllerImplTest.RequestPermissionsDelegatesIffMissingOverrides:PermissionControllerImplTest.GetPermissionStatusDelegatesIffNoOverrides:PermissionControllerImplTest.GetPermissionStatusForFrameDelegatesIffNoOverrides:PermissionControllerImplTest.NotifyChangedSubscriptionsCallsOnChangeOnly:PermissionControllerImplTest.PermissionsCannotBeOverriddenIfNotOverridable:PermissionControllerImplTest.GrantPermissionsReturnsStatusesBeingSetIfOverridable:PictureInPictureServiceImplTest.EnterPictureInPicture > > Curious developers can binary search in that short list of tests to find > the one(s) that are leaking and clean them up. > > BUG=546640 > TBR=sky@chromium.org > > Change-Id: If3be7034094827979c225d2eb2beba2d92e6e7ce > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978679 > Commit-Queue: Greg Thompson <grt@chromium.org> > Auto-Submit: Greg Thompson <grt@chromium.org> > Reviewed-by: Erik Chen <erikchen@chromium.org> > Cr-Commit-Position: refs/heads/master@{#728475} TBR=sky@chromium.org,erikchen@chromium.org,grt@chromium.org,isamsonov@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 546640 Change-Id: Ic1d52021e5505508d271f2b1932f00c3e77377be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991933Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#729487}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/bd5874accf0f..28209b43f4a1 git log bd5874accf0f..28209b43f4a1 --date=short --first-parent --format='%ad %ae %s' 2020-01-08 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 086dd4c4..4bca0ab4 (729202:729323) 2020-01-08 jakobi@webrtc.org Remove extra delay field trial. 2020-01-08 srte@webrtc.org Moving FakeNetworkSocket to fake_network_socket_server.h 2020-01-08 srte@webrtc.org Cleanup: Removes redundant includes on message_queue.h Created with: gclient setdep -r src/third_party/webrtc@28209b43f4a1 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 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ic1a5708f42e66997b8358c94c283daab743bc526 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991781Reviewed-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@{#729486}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/b84cdffeec6c..99c274baf503 git log b84cdffeec6c..99c274baf503 --date=short --first-parent --format='%ad %ae %s' 2020-01-08 tobine@google.com Vulkan:Roll volk Created with: gclient setdep -r src/third_party/angle@99c274baf503 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 cwallez@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/+/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 Bug: None Tbr: cwallez@google.com Change-Id: I01608361bb3aeb55c2dd38ecf0335fb800ab2f3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992111Reviewed-by:
-
sebsg authored
This reverts commit 11d5c38e. Reason for revert: Several virtual/controls-refresh/ webkit layout tests failing on Mac 10.10 More details at crbug.com/1040231 Bug: 1040231 Original change's description: > Color control popup UI improvements > > This CL updates the <input type="color"> popup UI in three related aspects per design feedback: > > 1) The in-page control now updates immediately as the selected color is changed in the popup, > instead of waiting for the popup to be dismissed. The page can watch for these 'live' changes > via the input event. > 2) The UI is simplified by removal of the submit and cancel buttons. The popup is now > dismissed only by clicking outside of it or with the Enter or Escape keys. > 3) A 'double-escape' model is introduced in which if a user has opened the popup and changed the > value, hitting Escape once will reset the value back to what it was when the popup was opened. > Hitting Escape once more, when the popup value matches the value when opened, will dismiss the > popup. > > Bug: 1001571 > Change-Id: Ifb918d5479efedb0e2fbe571d4239bc15cbcc723 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978252 > Reviewed-by: Sanket Joshi <sajos@microsoft.com> > Reviewed-by: Mason Freed <masonfreed@chromium.org> > Commit-Queue: Dan Clark <daniec@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#729387} TBR=hwi@chromium.org,masonfreed@chromium.org,daniec@microsoft.com,sajos@microsoft.com Change-Id: Iebd75210a136360cf51647bf36b0d04e4a2643e5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1001571 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992560Reviewed-by:
sebsg <sebsg@chromium.org> Commit-Queue: sebsg <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#729484}
-
Sean Harrison authored
Dark mode versions are coming later Bug: 1014143 Change-Id: I59bdbaa7c0faa7bca59507f45ea0ae9d0b7e6776 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978738Reviewed-by:
Dan Beam <dbeam@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Sean Harrison <harrisonsean@chromium.org> Cr-Commit-Position: refs/heads/master@{#729483}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/7d0ce41d01de..c45e066fba2d git log 7d0ce41d01de..c45e066fba2d --date=short --first-parent --format='%ad %ae %s' 2020-01-08 bclayton@google.com Vulkan/Debug: Add Reference value type. 2020-01-08 chrisforbes@google.com Add storage image support for R16G16_{UINT,SINT,SFLOAT} Created with: gclient setdep -r src/third_party/swiftshader@c45e066fba2d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I0fdc96bf39da9109a2bd721bbb4e58aa6d42152b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992114Reviewed-by:
-
David Black authored
Previously, it was possible to open the Assistant Web UI container and then disable Assistant in the background which would cause our container to persist when it should actually be destroyed. Bug: b:147344165 Change-Id: Ia65070fb4d108efb967232f767628e91454d9f8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992312Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/master@{#729481}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9506caf2ea1f..a47e1e9794a7 git log 9506caf2ea1f..a47e1e9794a7 --date=short --first-parent --format='%ad %ae %s' 2020-01-08 jbudorick@chromium.org devil: add more logging on failure to kill host_forwarder. Created with: gclient setdep -r src/third_party/catapult@a47e1e9794a7 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC oysteine@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/+/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_optional_gpu_tests_rel Bug: chromium:1038789 Tbr: oysteine@google.com Change-Id: I55d2f71354fa401b547ab5ddcb27ba276ec99ad1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992401Reviewed-by:
-
Charlene Yan authored
Bug: 1033962 Change-Id: Idbc5d1108a43d6de1637f40caddadfa42be005fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990334Reviewed-by:
Charlene Yan <cyan@chromium.org> Reviewed-by:
Connie Wan <connily@chromium.org> Commit-Queue: Charlene Yan <cyan@chromium.org> Cr-Commit-Position: refs/heads/master@{#729479}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/403c80797189..5c660e0cd868 git log 403c80797189..5c660e0cd868 --date=short --first-parent --format='%ad %ae %s' 2020-01-08 mtklein@google.com Streamline skvm bilerp. 2020-01-08 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2020-01-08 egdaniel@google.com Reland "Move makeDeferredRenderTargetContext calls to factory on RTC." 2020-01-08 jvanverth@google.com Add method to delay drawable acquisition from MTKView 2020-01-08 rmistry@google.com Revert "Prevent de-duplication of Housekeeper-PerCommit-BuildTaskDrivers" 2020-01-08 kjlubick@google.com [canvaskit] Add webp support 2020-01-08 egdaniel@google.com Add debug gpu abandon bots and fix yuv crash. 2020-01-08 halcanary@google.com Reland "GrGLMakeNativeInterface_{iOS,mac,win}: clean up" 2020-01-08 mtklein@google.com add Brian's fiddle as gm/bicubic Created with: gclient setdep -r src/third_party/skia@5c660e0cd868 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC jvanverth@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: jvanverth@google.com Change-Id: I833376a237a65446bb89e6c507ca560be9fee952 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992116Reviewed-by:
-
Matt Menke authored
The tests use an HttpServer run over a Mojo connection, but they don't ensure that the HttpServer has started listening for connections before trying to establish a connection to the server over a client socket (also used over Mojo). The tests seem to be passing, but it sometimes times out on Fuchsia, when the HttpServer tries to accept a second socket. This seems likely due to some other bug (possibly in the Fuchsia socket layer), but regardless of the underlying cause, having the test fixture wait for the server to start listening seems to make the test consistently pass, and is something the tests should be doing anyways. Bug: 1032620 Change-Id: I48b57e99923189496d4e405f84a22767ca42a68a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992205Reviewed-by:
Maksim Orlovich <morlovich@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#729477}
-
Mason Freed authored
This is just a re-organization of the expectations for crbug/com/1035582, to make it easier to rebaseline without merge conflicts. TBR=schenney@chromium.org Bug: 1035582 Change-Id: I46ac7b5fc496654cc08e9020b6b327bfbc606896 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991734Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#729476}
-
danakj authored
OOPIF RenderWidgets had no way to see that their RenderView was created with a flag saying that the RenderWidget would never be visible. So we store that flag on RenderViewImpl and give it to each RenderWidget created thereafter. This allows RenderWidgets other than an initial main frame one to see this flag. Also, OOPIF child frame RenderWidgets were not being given the display mode during creation, unlike other RenderWidgets. Make this consistent and give the display mode. R=dcheng@chromium.org Bug: 419087 Change-Id: I44a25a13855c567516b813c90d195c836d90ebd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989239 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#729475}
-
Chris Hamilton authored
The remaining PerformanceManager.SiteInstance* metrics will end up being identical to the various PerformanceManager.Agent* once site instance = agent, which is part of ongoing site instance and blink isolate work. One variant of those metrics can then be removed at that point. Fixed:995541,1038476 Change-Id: I0a6eca14a5a857ebc2de082165cb60055269d71c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989686 Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Auto-Submit: Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#729474}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/cce82035ba5b..7f86589d1522 git log cce82035ba5b..7f86589d1522 --date=short --first-parent --format='%ad %ae %s' 2020-01-08 fmayer@google.com Do not use recursion for walking heap graphs. Created with: gclient setdep -r src/third_party/perfetto@7f86589d1522 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 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/+/master/autoroll/README.md Bug: chromium:147125938 Tbr: perfetto-bugs@google.com Change-Id: I72a1c85025a5f970553eca402cf58c708aa82fcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992100Reviewed-by:
-
gogerald authored
We do not support them for now. Screenshot: https://drive.google.com/a/google.com/file/d/1K9s8sgchCHchh0Xv3XuXVB-9Von_DbuP/view?usp=sharing Bug: 1028524 Change-Id: I2d83e0e93297950024d9d327132e3e1a8a8a8ba1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980285Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#729472}
-
Devlin Cronin authored
Remove ExtensionBrowserTest::WaitForExtensionInstallError() and ChromeExtensionTestNotificationObserver::WaitForExtensionInstallError(). The latter was only called by the former, which in turn was only called in a single place. Inline the (short) implementation directly into the single test that called it. In addition to removing cruft from the (very large) ExtensionBrowserTest interface, this also fixes a potential issue: the proper pattern for these types of observers is: <instantiate test observer> <trigger behavior> <wait with test observer> Here, it was: <trigger behavior> <instantiate and wait with test observer> This is can be racy or incorrect depending on the triggering behavior, since it may already finish before the observer is instantiated. Bug: None Change-Id: If35c9faff6ac60e86b476c5064ad0d0d1dd7f739 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981050 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Cr-Commit-Position: refs/heads/master@{#729471}
-
sebsg authored
This reverts commit eba0ee5c. Reason for revert: Test failures on Linux CFI related to Dav1d tests. More details at crbug.com/1040107 Original change's description: > Roll src/third_party/dav1d/libdav1d/ 940eee483..115fe773f (26 commits) > > https://chromium.googlesource.com/external/github.com/videolan/dav1d.git/+log/940eee483a85..115fe773fe0e > > $ git log 940eee483..115fe773f --date=short --no-merges --format='%ad %ae %s' > 2020-01-07 dalecurtis Fix missing include for limits.h > 2020-01-05 martin arm64: msac: Avoid 32 bit intermediates in symbol_adapt > 2020-01-02 martin arm64: itx: Use sqrdmulh in the preexisting identity transform functions > 2020-01-01 martin arm64: itx: Specialcase transforms with identity in the first pass with downshift > 2020-01-02 martin arm64: itx: Adjust .irp in the 4x16/16x4/8x16/16x8 functions > 2019-12-31 rsbultje Don't interleave the skip mode index finding loops > 2020-01-01 rsbultje Prevent shift by >= 32 > 2019-12-31 rsbultje Take lossless into account when assigning loopfilter strength > 2019-12-31 rsbultje Deal with chroma coefficients that are exactly 0x100000 > 2019-12-31 gramner x86: Fix inverse (flip)adst 8x4 clipping > 2019-12-31 gramner Fix C inverse ADST clipping > 2019-12-28 rsbultje av1: use chroma txtp inference over default DCT_DCT if qidx=0 > 2019-12-28 rsbultje av1: skip super-resolution upscaling if width < 16 > 2019-12-28 rsbultje av1: do C inverse transforms in int32_t precision > 2019-12-28 mjbshaw Allow skip mode > 2019-12-28 mjbshaw Disable warping on scaled references > 2019-12-23 rsbultje Check skip flag before setting tx context to TX_4X4 in lossless frames > 2019-12-18 martin Don't assume dlsym exists on linux > 2019-12-12 gramner Linux: Add a workaround for a glibc stack size issue > 2019-12-14 gramner x86: Disable AVX-512 by default > 2019-12-14 gramner Fix potential race condition in dav1d_get_cpu_flags() > 2019-12-14 gramner x86: Remove unused cpu flags > 2019-12-14 e.m.terhoeven Add support for Ice Lake AVX-512 cpu flags > 2019-12-13 rzumer Correct the edge buffer documentation > 2019-12-05 ltrudeau Move lvl variable in cdef_brow to outer loop > 2019-11-03 rsbultje Simplify shifting in generate_grain_y/uv AVX2 > > Created with: > roll-dep src/third_party/dav1d/libdav1d > > Change-Id: I19174ac159addacbe3b63016ce46a30425abd4f3 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989729 > Commit-Queue: Dale Curtis <dalecurtis@chromium.org> > Reviewed-by: Thomas Guilbert <tguilbert@chromium.org> > Cr-Commit-Position: refs/heads/master@{#729186} TBR=dalecurtis@chromium.org,tguilbert@chromium.org Change-Id: I815a01f90db85775d1695de8c4feb3bdb059b4b0 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992212Reviewed-by:
-
Balazs Engedy authored
Extend the lifetime of the histogram until M90. Bug: 1037001 Change-Id: I5c167a4e89187d284b1da142ec771184cf2b75e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989074Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
-
Aran Gilman authored
This allows DOM Distiller's JS code to be more consistent with other Chromium code. Bug: 1027612 Change-Id: I837f00e68eada2b5ff0f3026b725497ac8c44a41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1954705 Commit-Queue: Aran Gilman <gilmanmh@google.com> Auto-Submit: Aran Gilman <gilmanmh@google.com> Reviewed-by:
-
Elly Fong-Jones authored
The flags UI javascript assumed that 'change' events on form controls could only be fired in response to user actions, which are impossible until the form controls are actually created and populated with their correct values. However, during form control restoration, 'change' events may get dispatched for select elements that are having their state restored. This confuses the UI javascript and causes it to send a malformed message to the browser, which in turn crashes the browser. This change: 1) Makes the webui message handler resilient against this kind of malformed message 2) Makes the webui javascript not send this kind of malformed message to begin with Bug: 1038638 Change-Id: I118c04217d8b3877bd0b35cc00b9bd24d073c009 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989513 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#729467}
-
Andrew Grieve authored
Causes "git cl format" and "git cl upload" presubmit checks to format changed lines in a review to adhere to our style guide (PEP-8). Bug: 846432 Change-Id: I8844a0a2086901995f26f7e078e762b348c04561 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989690 Auto-Submit: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#729466}
-
gogerald authored
Screenshot: https://drive.google.com/a/google.com/file/d/1G50gW-Rb8gzN7hrQx1RN6hBYnRliDc_h/view?usp=sharing Bug: 990979, 1005930 Change-Id: I6b43fef85063d4a61759a71979014dfda6adfc24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988230Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#729465}
-
Andrey Kosyakov authored
This fixes a case when HeadlessExperimental.beginFrame method never resolves its callback when invoked with screenshot requested at the times where root layer is not available (e.g. if we haven't seen the start of the document yet). - fire beginFrame callback early in ExternalBeginFrameSourceMojo if some surfaces are still pending when all frame sinks have reported the frame as finished; - also discard all pending requests of output if we're firing frame callback without producing the frame above. Bug: 997946, b/146430148 Change-Id: Ib45b35474c7c1a15263a215747928970ecfa3c1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1987298 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#729464}
-
Will Harris authored
This can happen if an Administrator resets the password of a user as per https://support.microsoft.com/en-us/help/309408/how-to-troubleshoot-the-data-protection-api-dpapi Before this CL, the operation would fail on each browser start and the AEAD key would not be set correctly, causing encryption operations to fail repeatedly. This CL changes behavior to regenerate a new key upon a failure. Note: all old data is still lost upon changing user's password in this way, but now data encryption will function from that point onward. TEST=manual, repro steps in the bug. BUG=1036277 Change-Id: I21f7a5645db9734277fbfddb193ce437dd4c1f51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989854 Commit-Queue: Will Harris <wfh@chromium.org> Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Cr-Commit-Position: refs/heads/master@{#729463}
-
Min Qin authored
The related feature is still in experiment, delay the expiration date to M83 BUG=1037047,1037048 Change-Id: I78fe70a37508dafe6f48fd86b235d2f5f4af84c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986890 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#729462}
-
Eric Stevenson authored
A common cause of UnsatisfiedLinkErrors is that the native library hasn't been loaded yet. It's difficult to tell the difference between this and other UnsatisfiedLinkErrors. This CL adds generated code that queries LibraryLoader to determine library loading status and throws an explicit error when a native method is called before the library has been loaded. Bug: 1022938 Change-Id: I63980990abaef16da3847a05eda01cb116779560 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976905Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Eric Stevenson <estevenson@chromium.org> Cr-Commit-Position: refs/heads/master@{#729461}
-
Sergey Ulanov authored
AudioRenderer interface allows StartTicking() to be called after Flush(). FuchsiaAudioRenderer wasn't handling this case correctly: it was calling AudioConsumer::Start() without Stop(). Fixed StartTicking() implementation to call Stop() when necessary. Also reversed order of arguments in Start(). Bug: 1027048 Change-Id: Id30a552b2bdebce51b9deec074605c06f4e852f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982798 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#729460}
-
gogerald authored
Bug: 1039970 Change-Id: Ib641bbac8af6a6fdce4f85a3955f060fb752d487 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992261 Commit-Queue: Ganggui Tang <gogerald@chromium.org> Reviewed-by:
-
Synthia Islam authored
If user attempts to change date value when max value below min, correct validation message will be shown. Bug: 979227 Change-Id: I0bb1d092ec3dcfb993c9622ff3e9986b6b0c35b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1916527Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#729458}
-
Henrique Nakashima authored
Use SharedPreferencesManager consistently instead of SharedPreferences directly. Bug: 1022108 Change-Id: Idb3389fcad53c9f7f936a054abe425ffd783b229 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988917Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Natalie Chouinard <chouinard@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#729457}
-
haozhe authored
Chrome and firefox passes all Bug: 1034538 Change-Id: I5c269ae99ab6a34cc70c238d1b6fb9f9eafb3eee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974696Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Hao Sheng <haozhes@chromium.org> Cr-Commit-Position: refs/heads/master@{#729456}
-
Tarun Bansal authored
Add field trial experiment to disregard |always_access_network| when computing the total prediction score. Change-Id: Ibc727a50499795953d6f49e43369a9c81b1c760e Bug: 1039025 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1984624Reviewed-by:
Egor Pasko <pasko@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#729455}
-
Vladimir Levin authored
This patch adds a perftest that verifies that child layout is skipped in a fieldset container. Verified run is ~700ms per iteration without render subtree and ~16ms with render subtree. R=chrishtr@chromium.org Bug: 966487 Change-Id: I0f5bf855f5933f182a3052682cbac3f870630ac8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991780Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#729454}
-
haozhe authored
Chrome passes all and firefox failed the translate-composition due to expect 'None' and got '0px' Bug Filed:https://bugzilla.mozilla.org/show_bug.cgi?id=1607313 Bug: 1034538 Change-Id: I1700cae51d539ea0d76ebe73efbaa6e038d6f5fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982776Reviewed-by:
-
dalyk authored
This change adds a new field, disable_secure_dns to the URLLoaderFactoryParams, which gets propagated to every URLRequest. Follow-up cls may add this param to worker URLLoaderFactories. Bug: 10161646 Change-Id: I81686054b38a7ef993c20eba274c8f8474317ac5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1888099Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Katharine Daly <dalyk@google.com> Cr-Commit-Position: refs/heads/master@{#729452}
-
Tibor Goldschwendt authored
Bug: 1032327 Change-Id: I4c8ac4b77c8c7676193ce4e50ded6d349f00ba20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986282 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
-
