- 10 Jan, 2020 40 commits
-
-
Glen Robertson authored
Change-Id: I92c88d9e681c11dc90a4b8a66f93280924b7bdf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994032 Auto-Submit: Glen Robertson <glenrob@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#730077}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/9eb28ddf2481..f72e48dd2ff0 git log 9eb28ddf2481..f72e48dd2ff0 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 5d178c93..e8ce929a (425 commits) 2020-01-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 c431d59626e1..12ce8f687d23 (8 commits) Created with: gclient setdep -r src/third_party/skia@f72e48dd2ff0 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: I572bdf841d046dcc3b3c393d3410cd49a6ddd242 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994248Reviewed-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@{#730076}
-
Timothy Loh authored
- Remove the START_DOWNLOADING state in the UI code. - Rename START_DOWNLOADING_DLC to STARTING and fix the initial state to be that. While we logically start installation immediately upon opening the dialog, we actually wait for AddedToWidget() to be called first, so retaining this state allows us to avoid confusion of being in an active state without having started the installation. - Remove the OnDlcDownloadStarted and OnDownloadStarted callbacks, the installer UI doesn't need these. - Add TODO suggesting further improvements regarding cancellation. Change-Id: I83575155047665139f0c1aa2af6b958b52df0b93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994846 Commit-Queue: Timothy Loh <timloh@chromium.org> Reviewed-by:
Julian Watson <juwa@google.com> Cr-Commit-Position: refs/heads/master@{#730075}
-
James Hollyer authored
When a Discovery Session is first started it can get into a state where it is pending another action to finish. If that action stops the discovery then the new session will get deactivated before it even begins. This change adds a status to the session so that we can count the discovery sessions which are scanning to see if we need to deactivate a session. Bug: 1039451 Change-Id: I86c0ae99b2546f57352e98c3b5b648d8144d0f7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988752 Commit-Queue: James Hollyer <jameshollyer@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#730074}
-
Sergey Senozhatsky authored
There is no driver actually generating events with this flag set. Since this is just downstream technical debt, which apparently isn't really needed and makes it impossible to compile Chromium with V4L2JDA enabled with upstream kernel headers, it's probably better to remove this flag. Bug: 942415 Test: Compile tested only (removing dead code). Change-Id: I3803d622d384e8e3831c201812a14c919e5bb4dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981412Reviewed-by:
Ricky Liang <jcliang@chromium.org> Reviewed-by:
Alexandre Courbot <acourbot@chromium.org> Auto-Submit: Sergey Senozhatsky <senozhatsky@chromium.org> Commit-Queue: Sergey Senozhatsky <senozhatsky@chromium.org> Cr-Commit-Position: refs/heads/master@{#730073}
-
Yuta Kitamura authored
This reverts commit 733e2fb1. Reason for revert: This CL caused a CHECK failure in the following browser_tests: LazyLoadDisabledBrowserTest.LazyLoadFrame_DisabledInBackgroundTab LazyLoadDisabledBrowserTest.LazyLoadFrame_DisabledInIncognito Sample run: https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/85969 CHECK failure log: > [67654:67654:0110/151505.705450:FATAL:embedded_test_server.cc(389)] > Check failed: !io_thread_.get(). Handlers must be registered before > starting the server. Original change's description: > Report save-data savings to LiteMode site-breakdown > > This CL gets the estimated data savings due to SaveData and updates as > LiteMode savings. The savings are retrieved from field trial as json. > > Bug: 923551 > Change-Id: Ia7c5518edfeaedce33e957c19224f6a2350df6c2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990989 > Commit-Queue: rajendrant <rajendrant@chromium.org> > Reviewed-by: Tarun Bansal <tbansal@chromium.org> > Reviewed-by: Ryan Sturm <ryansturm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#729972} TBR=tbansal@chromium.org,rajendrant@chromium.org,ryansturm@chromium.org Change-Id: I79ebf0d0a25d218ddbe644d708ba65d57061c92a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 923551 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994850Reviewed-by:
Yuta Kitamura <yutak@chromium.org> Commit-Queue: Yuta Kitamura <yutak@chromium.org> Cr-Commit-Position: refs/heads/master@{#730072}
-
David Bokan authored
This is a mechanical patch that turns uses of these methods in unittests into the newly added ScrollUpdate (which delegates to either of these under the hood) Bug: 1016229 Change-Id: Ie65dd5c5b702c625159e239ee0e5b7fc0552e3d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982236 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#730071}
-
Glen Robertson authored
Disable the "Install <PWA>" and "Create Shortcut" menu items when installing the current page would replace an externally-installed app. Fixed: 992312 Bug: 992312 Change-Id: Iaf8ebfdd0ddd0787b43211affd918c9a0c3a5e26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897398Reviewed-by:
Alan Cutter <alancutter@chromium.org> Commit-Queue: Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#730070}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/7a37d3acf532..12ce8f687d23 git log 7a37d3acf532..12ce8f687d23 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 kbr@chromium.org Upstream WebKit's iOS port of ANGLE. Created with: gclient setdep -r src/third_party/angle@12ce8f687d23 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: I408ae5acdd357c0dcb2b62e6aef17612b17951bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994244Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/0319809c5c5a..9dbcda838560 git log 0319809c5c5a..9dbcda838560 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 dberris@chromium.org Add dispatch.yaml and upload-processing.yaml to dashboard files Created with: gclient setdep -r src/third_party/catapult@9dbcda838560 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:1035930 Tbr: oysteine@google.com Change-Id: I9ec8ea87af22970ec6619d45c642e8481a02781a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994246Reviewed-by:
-
Andrey Kosyakov authored
This changes the type for std::vector arguments passed in wrapper class constructors and setters from reference to value (i.e. from const std::vector<>& in_param to std::vector<> in_param), so that std::move() that we invoke in the bodies of constructors and setters are actually effective. The effect of the change on generated files can be seen here: https://paste.googleplex.com/5618555812839424?raw Change-Id: Id9cfd3bf23257d2418d462f52a39f3b01e1de96c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990446Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#730067}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/1386c58de710..9eb28ddf2481 git log 1386c58de710..9eb28ddf2481 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 77c89ff847b6..110236f3ce70 (5 commits) Created with: gclient setdep -r src/third_party/skia@9eb28ddf2481 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: I7a1f12b5a8788d944f84b2c39bf524c704102052 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994245Reviewed-by:
-
Francois Buergisser authored
The writable buffer references are passing their buffers to the decode surface to set the controls, requests or config store settings which is making the writable buffer references aware of the decoded surface. This patch removes references to the decode surfaces in the writable buffer reference and at the same time simplifies to the decode surface submission. BUG=chromium:1009921 TEST=ran tast with video.DecodeAccelVD.vp8_resolution_switch on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.h264_resolution_switch on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.vp8 on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.h264 on veyron_minnie. TEST=ran tast with video.DecodeAccel.vp8 on veyron_minnie. TEST=ran tast with video.DecodeAccel.h264 on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.vp8_resolution_switch on kevin. TEST=ran tast with video.DecodeAccelVD.h264_resolution_switch on kevin. TEST=ran tast with video.DecodeAccelVD.vp8 on kevin. TEST=ran tast with video.DecodeAccelVD.h264 on kevin. TEST=ran tast with video.DecodeAccel.vp8 on kevin. TEST=ran tast with video.DecodeAccel.h264 on kevin. Signed-off-by:
Francois Buergisser <fbuergisser@chromium.org> Change-Id: I5097a2bb9b2ce1ede7e7ad573d37a47d15dfaf26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969411Reviewed-by:
-
Rachel Sugrono authored
Bug: 907380 Change-Id: I3d8c4d1c4457b6ee9a11d58fe23ce6402e4d6805 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994022 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#730064}
-
Koji Ishii authored
Following bot results are included. 890 891 892 893 896 897 898 3 lines were removed and 5 lines were deflaked by consecutive results since 877. TBR=yosin@chromium.org NOTRY=true Bug: 982194 Change-Id: I39807e59713191698b85fbf8498c264016cd9a33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993074Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#730063}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/aed6b2e7fbd5..079a14224dd1 Created with: gclient setdep -r src-internal@079a14224dd1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@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.chrome.try:linux-chromeos-chrome Bug: chromium:1039966 Tbr: jbudorick@google.com Change-Id: I00873da03898fe4fe02f45beb29126b276e15e51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994664Reviewed-by:
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/master@{#730062}
-
Xianzhu Wang authored
The new rules reflect the new path names for flag-specific expectations of composite-after-paint and disable-layout-ng. We also don't need linux-blink-rel for CompositeAfterPaint. Change-Id: I130107d4a81463cdccd656cd4c0a1172bb79a9d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994526Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#730061}
-
Christopher Cameron authored
We will need to parameterize more than just the usual 7-param custom transfer function. In particular: - PQ transfer function white point (SMPTEST2084) - Extended-sRGB white point (IEC61966_2_1_HDR) - CrOS part-linear, part-sRGB curve split-point and maximum-value Set us up for this by: - Rename ColorSpace::custom_transfer_params_ to just transfer_params_, to indicate that they are used for more than just CUSTOM. - Changing IPC serialization to simply copy all of transfer_params_, rather than trying to selectively not copy them (note that mojo always copies all of them) - Use the helper function TransferParamCount to query the number of parameters used Bug: 1037954 Change-Id: I9c52a1dc583dd24b57056131d468a5e18f83dc9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992323 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
-
Francois Buergisser authored
The queue's support is currently checked in the video decoder but the queue should be responsible to check whether it does support requests or not. This patch moves the check for the request support to the V4L2Queue constructor. BUG=chromium:1009921 TEST=ran tast with video.DecodeAccelVD.vp8_resolution_switch on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.h264_resolution_switch on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.vp8 on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.h264 on veyron_minnie. TEST=ran tast with video.DecodeAccelVD.vp8_resolution_switch on kevin. TEST=ran tast with video.DecodeAccelVD.h264_resolution_switch on kevin. TEST=ran tast with video.DecodeAccelVD.vp8 on kevin. TEST=ran tast with video.DecodeAccelVD.h264 on kevin. TEST=ran video_decode_accelerator_tests w/ vp8 & h264 videos but w/o VD on kevin. Signed-off-by:
-
Timothy Loh authored
The Plugin VM installation flow currently is driven by the UI side, with it calling into the installer after each step to start the next step. This CL changes this so after it starts the installation, the UI side doesn't need to call into the installer (aside from cancelling) and just needs to update what it displays to the user. This makes the flow easier to follow and reduces the coupling between the UI and the installer backend. It also makes it easier to make changes to the flow, for example adding additional steps. Bug: 1038816 Change-Id: Ice6a32a572c16a2bc32e86c166ff6e486791d877 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989722Reviewed-by:
-
Meilin Wang authored
This is a temporary fix. The real fix should be to migrate off Content Service and back to WebView (tracking bug: b/146351046). Misc: fix linter warning. Bug: b/144765770 Test: manually. Change-Id: I2aafbb30878374424597db7159d1777cb4fa1c20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992685Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Meilin Wang <meilinw@chromium.org> Cr-Commit-Position: refs/heads/master@{#730057}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/1f6ff4c2bb48..0319809c5c5a git log 1f6ff4c2bb48..0319809c5c5a --date=short --first-parent --format='%ad %ae %s' 2020-01-10 dberris@chromium.org Split off upload processing to a different service Created with: gclient setdep -r src/third_party/catapult@0319809c5c5a 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:1035930 Tbr: oysteine@google.com Change-Id: If96c0595eeda8103cab839aacb1ad82cb2dd475b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994675Reviewed-by:
-
Chromium WPT Sync authored
Using wpt-import in Chromium e61ad0df. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, lpz@chromium.org, robertma@chromium.org: external/wpt/tools jsbell@chromium.org: external/wpt/resources NOAUTOREVERT=true TBR=lpz No-Export: true Change-Id: I21d06d257d78753395d1682736b1f82479004758 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993716Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#730055}
-
Andrew Luo authored
Bug: 1019521 Change-Id: Idfc304e1f335a4d03d4cccdc9101584564236c53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980997Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/7a4290c4..1dacd66f 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,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8620e75ec411b6c7916d0b9e805874b67e63dca1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993761Reviewed-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@{#730053}
-
Alexandre Courbot authored
The format specifier for a int64_t argument was %ld, which works fine on 64-bit architectures but corresponds to a 32-bit long on 32-bit archs. Fix this by using the PRId64 specifier that will work on all architectures. BUG=None. TEST=Chrome builds for arm-generic. Change-Id: Iee32204df9f52fe2a6dd9ceb05edee22ff5e14f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993068 Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Auto-Submit: Alexandre Courbot <acourbot@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#730052}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I0b52e6f3fd5c45ad2058503e0321679daee0e374 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993905Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#730051}
-
Takashi Toyoshima authored
There was no test for verifying the code to reject CORS-enabled requests that do not have |request_initiator|. This patchset adds an unit test for FileURLLoaderFactory to verify request_initiator requirements for each RequestMode. Change-Id: I27b88075f0bb07d91268c2f25aa2f94b9ec321c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989432 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#730050}
-
Simon Que authored
They were incorrectly set to goma_backend=None. Bug: None Change-Id: If4a4654749ee3074b431825af39836814dab8cfd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994367Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Simon Que <sque@chromium.org> Cr-Commit-Position: refs/heads/master@{#730049}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ab81316411df..9b289b2c2973 git log ab81316411df..9b289b2c2973 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision d63380b8..aa827d65 (729869:729982) Created with: gclient setdep -r src/third_party/webrtc@9b289b2c2973 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: I0a1cc94d3addf90ff4f4543c7907e1beefd98996 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994674Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/697b2241a6c7..7a37d3acf532 git log 697b2241a6c7..7a37d3acf532 --date=short --first-parent --format='%ad %ae %s' 2020-01-09 kbr@chromium.org Work around Intel driver bug with CopyTex{Sub}Image2D/DeleteTextures. Created with: gclient setdep -r src/third_party/angle@7a37d3acf532 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: Ibe751691c0f6480f97ecb98605b80cb8b2391ac4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994663Reviewed-by:
-
Ahmed Fakhry authored
- The backdrop used to show immediately even if the window-needing-it is still animating, making the animation look poor. - There multiple recursive calls to UpdateBackdrop() constantly all the time, many of them are not necessary, and can be handled only by laying out the backdrop if needed. - Even the browser's status bubble used to cause multiple called to UpdateBackdrop() as the user moves their mouse hovering over links, which causes the status bubble to be created, removed, and have visibility changes. - The backdrop window itself causes calls to UpdateBackdrop as it gets shown and hidden. - The backdrops weren't showing in the desks mini_views (a regression caused by me). - WorkspaceLayoutManager and Desk were both updating the backdrops for the same event. This CL fixes the above issues. BUG=1031789 TEST=Manually, all backdrop tests should pass. Change-Id: I5e25705ae50abdf1cf69b63b01f762044587f600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974593 Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#730046}
-
Tibor Goldschwendt authored
Bug: 1032327 Change-Id: I55c34b77eaffb7573ce8fb020d102b9286d945e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993624 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#730045}
-
yilkal authored
This is a reland of 73d4b9c4 Original change's description: > Update WebTimeLimit url filter > > This cl does the following: > 1. Adds PrefChangeRegistrar to AppTimeController to enable it > to be notified when user policy has changed. > 2. Enables prefs::kPerAppTimeLimitsWhitelistPolicy policy to be > used in WebtimeLimitEnforcer. > > Bug: 1015661 > Change-Id: Ifd5e0ddc3df9f564ffb018244e652c8b88586865 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946936 > Commit-Queue: Yilkal Abe <yilkal@chromium.org> > Reviewed-by: Aga Wronska <agawronska@chromium.org> > Cr-Commit-Position: refs/heads/master@{#729598} Bug: 1015661 Change-Id: I641c293db66f1d0eb221a3015d1c14864512b3d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993021 Commit-Queue: Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#730044}
-
Julie Jeongeun Kim authored
This is a part of effort for using [RaisesException] when synchronously rejecting a promise. It uses [RaisesException] for //third_party/blink/renderer/modules/webaudio. Bug: 1001114 Change-Id: Ifb03c0cce7d61621be8c34774ccc49c3b1debe56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986469 Commit-Queue: Julie Kim <jkim@igalia.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#730043}
-
Demetrios Papadopoulos authored
Also stop subclassing MojoWebUIController from SettingsUI on CrOS, since it is no longer needed. Bug: 990166 Change-Id: I4966e2aac58cba46d0245025037b878f77b07397 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992989Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#730042}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/a7e42ba7f855..110236f3ce70 git log a7e42ba7f855..110236f3ce70 --date=short --first-parent --format='%ad %ae %s' 2020-01-09 sugoi@google.com Enable filtering depth+stencil formats Created with: gclient setdep -r src/third_party/swiftshader@110236f3ce70 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: If7e2ffd07dffbbc06011a05ee606a4ca5edfe069 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994400Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ce9e11f02436..1f6ff4c2bb48 git log ce9e11f02436..1f6ff4c2bb48 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 rmhasan@google.com Revert "[Telemetry] Expose ChromeOS board tags" 2020-01-10 rmhasan@google.com Reland "[Typ] Allow typ expectations parser to escape the '*' character" 2020-01-09 bsheedy@chromium.org [Telemetry] Expose ChromeOS board tags Created with: gclient setdep -r src/third_party/catapult@1f6ff4c2bb48 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:1036130,chromium:1038726 Tbr: oysteine@google.com Change-Id: Ic932d1e9adc15925f8f41e9b4e421dcb626770f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994660Reviewed-by:
-
Jimmy Gong authored
- Needed so that the JS layer can call on queryPrintServer. - Updates browsertests to reflect this change. Bug: 1015628 Test: browsertests Change-Id: I3bcb69b6f0e3426231ae14443378eb27bcf490d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1950890 Commit-Queue: jimmy gong <jimmyxgong@chromium.org> Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#730039}
-
Tom Anderson authored
On some notification daemons (at least lxqt-notificationd and naughty), the icon is not downsized to a reasonable size. Rather than changing the icon size depending on which notification daemon is running, this change always uses 64x64 icons for a few reasons: * There may be more daemons that have this behavior. * There's no realistic situation to my knowledge where 256x256 is desired. * In most other situations, the daemon will downsize the icon anyway, so it's best to not needlessly waste resources for the common case. R=thestig Bug: b/146459375 Change-Id: Ib841b6cce17be9043f5e81eabb44188da3b51b27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994389 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#730038}
-
