- 29 May, 2020 33 commits
-
-
Minoru Chikamune authored
HeapMojo wrappers can reset the mojo objects automatically. So no need to reset mojo objects in prefinalizer again. Bug: 1049056 Change-Id: Iaa0e99857eee508c6026d0aaba1356fbc8315a72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217719Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Minoru Chikamune <chikamune@chromium.org> Cr-Commit-Position: refs/heads/master@{#772983}
-
Minoru Chikamune authored
HeapMojo wrappers can reset the mojo objects automatically. So no need to reset mojo objects in prefinalizer again. Bug: 1049056 Change-Id: Ib7276458a9edf9372f4d7cbae13cfa7ceae267ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217720Reviewed-by:
-
Minoru Chikamune authored
HeapMojo wrappers can reset the mojo objects automatically. So no need to reset mojo objects in prefinalizer again. Bug: 1049056 Change-Id: I6119eda011fb9dd06f95f1e1fd6db0e3778db321 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217526Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/1a4975642bf9..45b9192ad981 2020-05-28 kron@webrtc.org Add trace of enqueued and sent RTP packets 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I3448df985e09a14c390b81ff3dec622c1b7b0ccd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220692Reviewed-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@{#772980}
-
Kyle Horimoto authored
This improves discoverability of the app, which was previously only available by clicking a link in settings or by right-clicking the desktop. Fixed: 1086197 Change-Id: Ia8037f3639ec33613cecef0aeb780b59b65cf5cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220337 Commit-Queue: Dominick Ng <dominickn@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#772979}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Ie685dca794d6e8de0ba04c320109b818fcb11de9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220617Reviewed-by:
-
Fabian Sommer authored
Stop observing with scoped observers when the observed objects are destroyed. Fixed: 1086124 Change-Id: Ib0aa9e6eb3dc346a441ecdd0416649622ff03f17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215056Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#772977}
-
David Bertoni authored
on on Windows and Mac. TBR=rockot@google.com Bug: 1066138 Change-Id: I0ea1bf603f53872cd75f3af8683c69765426cd40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220361Reviewed-by:
David Bertoni <dbertoni@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#772976}
-
David Bertoni authored
TBR=johnidel Bug: 1087406 Change-Id: I122cacf54ec7e000da17a29ead3c189c10c342cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220501Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b28e75d6..468f8fff Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Iaf58dd730b850549ed34298cdc6debd9056aefc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218390Reviewed-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@{#772974}
-
Yuly Novikov authored
Since these tests use the native windowing system and thus need Xvfb when they run on GCEs. And also because these tests need to be wrapped by test_env.py to set up correct environment variables on ASAN, TSAN and CFI bots. gl_unittests already had it, but gl_tests did not, since they were "raw" isolate type. Unfortunately, gl_unittests had to be removed from 'Linux MSan Tests' as the result, for the same reason gl_tests were removed in crbug.com/830659. Probably a meaningful codepath was not tested before anyway. On another hand, gl_unittests can pass on GCEs now, so also removed the exception to launch them on HW GPU machines for Linux CFI bots, making them consistent with ASAN and TSAN bots. Also had to suppress a leak in NVIDIA libraries, since ASAN now really runs and detects it. And a minor cleanup removing 'use_xvfb' flag which is irrelevant for Swarming bots. Bug: 1081054 Change-Id: Iec8c2e3f54505eca6ae22333c86759a9553ed799 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199670 Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#772973}
-
Dominic Farolino authored
We're interesting in implementing the HTML Standard notion of a parser document [1], which will replace CreateElementFlags::created_by_parser_ with a pointer to the document that the parser was created for. Therefore when marking a CreateElementFlags object as created-by-parser, one should also provide the document for the parser. As a part of this we're looking at all of the call-sites of CreateElementByFlags::{ByParser(),SetCreatedByParser()} to see which are actually related to parsing an HTML Document and require parser-inserted information. It seems that the VTT usages of CreateElementFlags::ByParser is unnecessary as it doesn't have anything to do with parsing an HTML document, and the parser-inserted information is never not queried for elements created here. [1]: https://html.spec.whatwg.org/C/#parser-document R=hiroshige@chromium.org, kouhei@chromium.org Bug: 1086507 Change-Id: Id40ddc2f7d87652cee8d6f2832e307bdf8f05d46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216314Reviewed-by:Mason Freed <masonfreed@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#772972}
-
Moe Ahmadi authored
<dom-repeat> fires 'on-dom-change' event as soon as the items are updated in the DOM. This is a more accurate estimate of when the matches are rendered. This is still not 100% accurate since it take some time for blink to render the DOM. However this should be close enough and matches the local NTP implementation. Bug: 1087469 Change-Id: Ief9727ae89cb70d89fe04979d60268fef2a6eed9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220690 Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Auto-Submit: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#772971}
-
Maggie Chen authored
Disable Direct Composition support when CreateSwapChainForComposition() fails. Bug: 1074582 Change-Id: I466c3febba7b63ccb0fc9f648a4b9cfaa7d8deba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219387 Commit-Queue: Maggie Chen <magchen@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#772970}
-
Daniel Rubery authored
Enterprises where users have not enabled Sync should still receive real time reporting events with profile user name. Fixed: 1084815 Change-Id: Ib60d9a3d03680341aeb6a540002a53c25e017ccd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215452 Commit-Queue: Daniel Rubery <drubery@chromium.org> Reviewed-by:
Bettina Dea <bdea@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#772969}
-
Ken Rockot authored
Types tagged with the [Stable] attribute can only depend on builtin mojom types or other user-defined types tagged with the [Stable] attribute. This attribute can be used to indicate that a mojom definition is safe to rely upon in situations where version skew must be tolerated. A follow-up CL will introduce a presubmit to ensure that types marked [Stable] do not change in a way that breaks backward-compatibility. Bug: 1070663 Change-Id: Ib7d966c15742f6acd6c8c12cd1ce3fee55aba7cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218803 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#772968}
-
Zhenyao Mo authored
BUG=1085729,1086820 TEST=manual R=rockot@google.com Change-Id: I6a5629a421753fa0e3d100f111e7251e78411bc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220660 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Auto-Submit: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#772967}
-
Scott Violet authored
If the height of the controls changes, then SynchronizeVisualProperties() needs to be called so that the renderer knows. Additionally, it appears that if the height changes onOffsetsChanged() isn't called. This ensures that happens. BUG=1086493 TEST=testRemoveAllFromTopView Change-Id: Ib978f50b3ea9c9bcee3adfd0f60bbd83d3e40eda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215460Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#772966}
-
François Degros authored
BUG=912236 TEST=browser_tests --gtest_filter="ZipFiles/*" TEST=browser_tests --gtest_filter="*/FilesApp*" Change-Id: Ica61d18e69555fa1d1fc136e51b462c16ad83d29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217766Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: François Degros <fdegros@chromium.org> Cr-Commit-Position: refs/heads/master@{#772965}
-
Klaus Weidner authored
The EGL_ANDROID_native_fence_sync isn't reported as present to applications, so Chrome uses heuristics to infer if it's present. It's not usable in emulation or for SwiftShader. SurfaceControl assumes that GpuFence support is available, so don't use it if native fence sync is unavailable since that's used to implement GpuFence on Android. This check already existed but duplicated logic from gl_surface_egl, replace this with a feature check. Bug: 1086736 Change-Id: Ie2db42f605cb3eb90726b36b1bb264b4190bef80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217036Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
-
Karandeep Bhatia authored
Extension installation through the webstore involves creation of a dummy extension with an empty extension root path. The empty extension root path causes DNRManifestHandler::Parse to incorrectly raise an error while validating the paths for the extensions' ruleset files. This happens because ExtensionResource::empty() just checks whether the extension root path is empty. Fix this by replacing the ExtensionResource::empty() check with a more comprehensive check. BUG=1087348 TEST=Ensure https://chrome.google.com/webstore/detail/ajfdfkmbjmdjekckfgibicedaabjoong installs correctly. TBR=rdevlin.chronin@chromium.org Change-Id: I4e58cef19da771b17cc1d1541ccc7424b5b6f3af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219779 Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Auto-Submit: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Kelvin Jiang <kelvinjiang@chromium.org> Cr-Commit-Position: refs/heads/master@{#772963}
-
Xiyuan Xia authored
EventGenerator uses WindowEventDispatcherObserver to throttle the mouse events. This does not work with nested loops in window moving/resizing or drag-n-drop. The mouse move event that triggers the nest loop does not finish until the nest loop quits. However, without further mouse events, the operation stalls and the nested loop would not quit. This CL revises the throttling part. It assumes that hitting the message pump implies the processing of the current event finishes and schedules the next event when that happens. Bug: 1032766 Change-Id: Ib32f06aa6d93b36372ea2b21d941e04293dbde2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220655Reviewed-by:
Jun Mukai <mukai@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#772962}
-
Darren Shen authored
This CL is a followup of https://crrev.com/c/2212198. IMEBridge is only used for Chrome OS, so move IMEBridge to a Chrome OS specific folder. Note, this CL changes the word NULL in comments to nullptr to pass a presubmit check. Bug: 1083803 Change-Id: I8e962996f59c7cebf7a95503ec957e5f57065f39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214590 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#772961}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 99cdc265. With Chromium commits locally applied on WPT: 6956d3da "Avoid repeating a single row/column of tiled background images" 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: rego@igalia.com: external/wpt/css/css-grid NOAUTOREVERT=true TBR=smcgruer No-Export: true Change-Id: Ia33ccf13537959dff7a6400cf9e7e3638c35d3a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217877Reviewed-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@{#772960}
-
Christian Biesinger authored
This fixes a DCHECK, see https://crbug.com/991096#c29 Bug: 991096 Change-Id: I94bad7bc6a637754dbaf5b402d166cb27ab36574 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220283 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#772959}
-
Sigurdur Asgeirsson authored
Bug: 1080672 Change-Id: Ib075e13fc02c8527f14e6e2e86eaa0a627c54f1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218542 Commit-Queue: Joe Mason <joenotcharles@chromium.org> Auto-Submit: Sigurður Ásgeirsson <siggi@chromium.org> Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#772958}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/4504fd580a5f..090475cde4fa 2020-05-28 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: agable@chromium.org Change-Id: I6ad58ce0ae58c61f5cde1f50cf2a9bd6b6a22002 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220708Reviewed-by:
-
Dan Harrington authored
After all surfaces are detached, the model is eventually unloaded. The timeout used is configurable via finch parameter. Bug: 1044139 Change-Id: I015945215c1a0cc25fff92ccf20a5d72f52c7309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216037 Commit-Queue: Dan H <harringtond@chromium.org> Reviewed-by:
Carlos Knippschild <carlosk@chromium.org> Cr-Commit-Position: refs/heads/master@{#772956}
-
Patrick Monette authored
This CL adds the ability for observers to know when a navigation for a window controllee commits to a RenderFrameHost. This is needed in the performance manager so that it is possible to connect service worker nodes to the frames it controls. The current OnControlleeAdded() notification does not include which render frame host this navigation is associated to because it is not known at the time OnControlleeAdded() is invoked. Bug: 993029 Change-Id: I91032a3ad606aceb98ae346e5f76bfec01cd4cfb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212808 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#772955}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8fcb597f7e06..251f6d529453 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 lgrey@google.com,dbertoni@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1021757 Tbr: lgrey@google.com,dbertoni@google.com Change-Id: I68897d827adab83e3731163f540c5d282d3579e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220583Reviewed-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@{#772954}
-
Amruth Raj authored
Sometimes, the Browser process tags events with kRelativeMotionEvent. For e.g. during pointer lock, it recenters cursor by warping so that cursor does not hit the screen boundary. In such a case the renderer is only supposed to update it's co-ordinates and not send these fake events to the DOM. This patch correctly suppresses pointerrawupdate events tagged with kRelativeMotionEvent from getting forwarded to the DOM. Bug: 1066544 Bug: 868660 Change-Id: Ib0a7337e3535a9719182bb1153038af11b6e9742 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217928Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Mustaq Ahmed <mustaq@chromium.org> Reviewed-by:
Ella Ge <eirage@chromium.org> Reviewed-by:
Vincent Scheib <scheib@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#772953}
-
Matt Menke authored
In particular, separate out the HSTS and ExpectCT data tables (addressing an old TODO) and switch from a dictionary of dictionaries to a list of dictionaries, so that ExpectCT entries can be keyed on NetworkIsolationKey in addition to domain hash in a followup CL. The current plan is not to partition HSTS information by NetworkIsolationKey, but this CL also switches it to using a list, to be similar to the ExpectCT table. This CL also adds a version number to the saved data format, and adds an empty NetworkIsolationKey field to ExpectCT entries, so that entries won't be lost when that field is added (though entries may be lost when switching from an empty NIK to actually applying NIKs, which is an issue for another day). Bug: 969893 Change-Id: If723386b7ebc447ae78cb393b6b9d6719441759d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216040 Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:
Nick Harper <nharper@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#772952}
-
Johann authored
Work has been done already to ensure the frame associated with the controller is not null. Following this down allows making Start() and Stop() protected which also removes the need to protect against various combinations of states. Bug: 850619 Change-Id: Ie1165322b231d72cb216645cde6f379ca52ed903 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214975Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: Johann Koenig <johannkoenig@google.com> Cr-Commit-Position: refs/heads/master@{#772951}
-
- 28 May, 2020 7 commits
-
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I89b70ded15144650048b5b5415cd78fdedb82614 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220229Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#772950}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e60ccbbb1b1d..a075151a2121 2020-05-28 oksamyt@google.com Parameterize raw_metrics_per_core with table name 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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: chromium:156788923 Tbr: perfetto-bugs@google.com Change-Id: I5418509dec46f1c272ec8f1214a3057eec8df59d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220654Reviewed-by:
-
Kyle Horimoto authored
This CL returns parent results (i.e., section or subpage results corresponding to the parent of another result). Two new parameters are added to the API: max_num_results (self-explanatory) and parent_result_behavior, which indicates whether the client would like to receive parent results or not. This CL modifies the settings UI to request parent results but defaults Launcher search back to the behavior before this CL, since Launcher search uses custom logic for this behavior. Fixed: 1082249 Change-Id: Ic714fe025c05062ca587ad1069698a8fedb75a08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220486Reviewed-by:
Regan Hsu <hsuregan@chromium.org> Reviewed-by:
Jia Meng <jiameng@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Auto-Submit: Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Jia Meng <jiameng@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#772948}
-
Brandon Wylie authored
Bug: 1083917 Change-Id: I742c1fd6c698887a186df4f8ae28244a6db4a1d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215453 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#772947}
-
Lei Zhang authored
It's probably not useful, since LeakTracker::CheckForLeaks() isn't being called. Change-Id: I96b226e43698a859c934e45916514d5369927ee1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219177Reviewed-by:
Eric Roman <eroman@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#772946}
-
Collin Baker authored
This reverts commit a1906b31. Reason for revert: left in debug log statements Original change's description: > Extract capture state machine > > This moves much of the capturing logic to ThumbnailCaptureDriver which > doesn't depend on WebContents or video capture details. Instead, it > expects calls from its client on state changes and calls back into a > client interface to request, start, and stop capture. > > Since the new class is testable, this also adds unit tests. > > Bug: 1073141 > Change-Id: I5e458ce4e7ab04f2091e1af4c76ad701d6eda0d1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2208547 > Reviewed-by: Dana Fried <dfried@chromium.org> > Commit-Queue: Collin Baker <collinbaker@chromium.org> > Cr-Commit-Position: refs/heads/master@{#772842} TBR=dfried@chromium.org,collinbaker@chromium.org Change-Id: I21fd1f4887d1b45fa8ebd3948c7c9658fb3d8144 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1073141 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220807Reviewed-by:
Collin Baker <collinbaker@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#772945}
-
Brian Sheedy authored
Switches the GPU DirectComposition pixel tests off the permissive Sobel parameters and onto more specific parameters. As a prerequisite, also adds support for Gold's new ignored border thickness parameter when doing inexact matching, which significantly improves the usefulness of the Sobel filter in certain cases since the Sobel filter is not applied to the pixels along the border of the image. Bug: 1078914 Change-Id: I3ccef878ad53bf456dcfeabe7fd5bc04472dcd80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218708 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
-
