- 16 Oct, 2019 40 commits
-
-
Dirk Pranke authored
When we added support for running on Mac 10.14 in https://crrev.com/c/1333567 and 10.15 in https://crrev.com/c/1776218, we didn't update the global list of supported test configurations in blinkpy/web_tests/port/base.py, which means that a test expectation would have been ignored on those machines *unless* you happened to be running on a Retina machine (like a Macbook Pro), which is treated as the "mac-retina" port and not "mac-10.14". 10.14 and 10.15 are still not fully supported, as we don't support separate baselines for them and don't support 10.14 or 10.15-specific expectations. This CL just means that the tests will run and 'Mac' expectations will work correctly. Bug: 1014785 Change-Id: I43521c752ceee92f21ed4335ebe055c486cc8427 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864002 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Rakib Hasan <rmhasan@google.com> Reviewed-by:
Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#706555}
-
Jasper Chapman-Black authored
Bug: 1011921 Change-Id: Ic8ed94149f624620679d67a6d0f33cf28bd3634e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1856839 Commit-Queue: Jasper Chapman-Black <jaspercb@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#706554}
-
Parastoo Geranmayeh authored
TBR=sky@chromium.org Bug: 1015020 Change-Id: Ia71d6f25a54198b2210d706e7bfc9e8d663f0eb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864717 Commit-Queue: Parastoo Geranmayeh <parastoog@google.com> Reviewed-by:
Parastoo Geranmayeh <parastoog@google.com> Cr-Commit-Position: refs/heads/master@{#706553}
-
Yves Gerey authored
This is a reland of 9db0a32a Reason for reland: The problematic part (misconfigured test suite) has been removed. A proper test suite will be added in a follow-up CL. Original change's description: > Add builder for opus test in prevision of rolls. > > This CL introduces an ad-hoc builder for roll of opus into chromium. > 1/ Used as pres-submit validation. > 2/ Runs dedicated tests and benchmarks for a fixed Android model. > > The point 2/ shall be completed in follow-up CLs. > > Bug: chromium:1002973 > Change-Id: Idb5c8b46ab68d8a9d63a864594396ac021a22746 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816555 > Commit-Queue: Yves Gerey <yvesg@google.com> > Reviewed-by: John Budorick <jbudorick@chromium.org> > Cr-Commit-Position: refs/heads/master@{#704847} Bug: chromium:1002973 Change-Id: Idd7f8d79350b622180b0c5d212712ac4e64a40bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860020Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Yves Gerey <yvesg@google.com> Cr-Commit-Position: refs/heads/master@{#706552}
-
Brandon Goddard authored
This change addresses an issue in Datagrids where pressing the context menu key while the data grid has focus does brings up actions for whatever node is in the center of the grid instead of whichever node is currently selected. Notice how in the before clip, the center rows with primary keys 14-16 get deleted, but in the after clip, the selected rows get deleted as expected: Before: https://imgur.com/pcijlqq After: https://imgur.com/TBLokOy Longer Explanation: Since the data grid itself retains focus, it uses CSS classes to indicate the currently selected item in the grid. When using a mouse right-click to bring up the context menu, the event.target in the context menu handler points to whatever cell was clicked on, and the data grid can determine the corresponding node from the target. However, when the context menu key is pressed, the event.target refers to whichever cell is directly in the visible center of the grid, which is often not the "selected" row. This causes the unexpected behavior of performing actions on the center row instead of the selected row. The fix uses event.button to detect the case where the context menu handler was reached but no mouse buttons where used (either the context menu key or Shift+F10) and then grabs the currently selected node instead of the node from the event.target https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/button Bug: 963183 Change-Id: Ib501178f0075b0ccf536b20d12f602fc174f325c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729554Reviewed-by:
Lorne Mitchell <lomitch@microsoft.com> Reviewed-by:
Jeff Fisher <jeffish@microsoft.com> Commit-Queue: Brandon Goddard <brgoddar@microsoft.com> Cr-Commit-Position: refs/heads/master@{#706551}
-
Garrett Beaty authored
Bug: 1011908 Change-Id: I0199693b03d5f6db82f5805e9b5047b80e0ba79c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862247 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#706550}
-
Mirko Bonadei authored
In component build mode, static_libraries do not guarantee that all the exported symbols will be present in the shared library while source_sets pass all the objects file to the linker. Bug: webrtc:9419 Change-Id: I2091ec607bf8848825f18a748e10bcd939d55bd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865215Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Cr-Commit-Position: refs/heads/master@{#706549}
-
Xiaoqian Dai authored
Clamshell mode behavior will remain the same, i.e., tapping on the overview background will return to its previous state, it can either be in-app or home screen. Bug: 997885 Change-Id: I82624e44024e273a343c20e3707cb1d97e31d594 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864026Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#706548}
-
arthursonzogni authored
When a page is navigated away, every RenderFrameHostImpl are properly removed from find-in-page thanks to: https://chromium-review.googlesource.com/c/chromium/src/+/1254262 However, the problem is that a removed frame does not automatically remove its highlighted selections when it is removed. This patch clear the highlighted selection. If this CL is not applied, when users will go back to the page using the back-forward cache. They will continue to see the yellow highlight. Bug=1001087 Change-Id: Ied5d152d34210d66dfa9afc66b4b775f7cd82bc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841631 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#706547}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/79f2a7ff7c3b..e5cc32d92cbf Created with: gclient setdep -r src-internal@e5cc32d92cbf 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 TBR=jbudorick@google.com Bug: chromium:None,chromium:None Change-Id: I22c5bae015863af8ae8736b5f321384998ffd436 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864562Reviewed-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@{#706546}
-
Vladimir Levin authored
depends_on means that the feature is only enabled if the depended-on feature is enabled. implied_by means that the feature is automatically enabled when the implied-by feature is enabled. We want CSSContentSize to be implied-by DisplayLocking, not DisplayLocking to depend-on CSSContentSize. R=chrishtr@chromium.org, rakina@chromium.org Change-Id: I39f908dee3d7a0b99d1f727b41f76ae3c1a8efcd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863564 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#706545}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@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/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Id87590c9ae2e3dddf858cfb5886ce359245409a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865033Reviewed-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@{#706544}
-
John Budorick authored
This reverts commit 71c00bee. Reason for revert: https://ci.chromium.org/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/15783 etc Original change's description: > Welcome screen: Fix language list initialization > > Change ResolveLanguageListInThreadPool so that it uses AppLocale instead > of default locale if exists. > > Bug: 955397 > Change-Id: I6947dd89e297adea3fd019e38d083e45419ea282 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1704098 > Reviewed-by: Alexander Alekseev <alemate@chromium.org> > Reviewed-by: Denis Kuznetsov <antrim@chromium.org> > Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org> > Commit-Queue: Roman Aleksandrov <raleksandrov@google.com> > Cr-Commit-Position: refs/heads/master@{#706436} TBR=antrim@chromium.org,alemate@chromium.org,rsorokin@chromium.org,raleksandrov@google.com Change-Id: Ide67b58544ccedb1abf8d58f6c7baaa6ba092e4e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 955397 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865422Reviewed-by:
-
Sven Zheng authored
This change can deflake some tests. https://chromium-swarm.appspot.com/task?id=47e99ad537e07c10 Key log: [4056:4920:1015/120125.356:WARNING:profile_downloader.cc(250)] Loading profile data failed [4056:4920:1015/120125.356:WARNING:profile_downloader.cc(251)] Error: -11 [4056:4920:1015/120125.356:WARNING:profile_downloader.cc(252)] Response code: -1 [4056:4920:1015/120125.356:WARNING:profile_downloader.cc(253)] Url: https://lh5.googleusercontent.com/-ojmQNrzeV7Q/AAAAAAAAAAI/AAAAAAAAAAA/ACHi3rfg5XN95Zfmg7mltoIHmd3Ql0OVKw/s256-c-ns/photo.jpg The url is actually the user's profile picture. Bug: 1010568 Change-Id: Icc7ae2bb0599c6bdef089b66a8aa84fab7ece4c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864020Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Sven Zheng <svenzheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#706542}
-
Yusuke Sato authored
On ARC, the property is filled with a value in config.json in /usr/lib/arc-setup in the arc-setup binary. This CL does the same for ARCVM but with the same file in /usr/lib/arcvm. BUG=b:136128691 TEST=new unittests pass Change-Id: Iac8ff895b9a6da90585d5bc057e0bd1359e28754 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1861038 Commit-Queue: Yusuke Sato <yusukes@chromium.org> Auto-Submit: Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#706541}
-
Avery Musbach authored
Bug: 970013 Change-Id: Iebbbab09b4e1542136b79b730a53424c13ef8d05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864015 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#706540}
-
Piotr Pawliczek authored
Add ExternalPrintServersWhitelist policy that allows for filtering print servers defined in ExternalPrintServers policy. It also changes the format of JSON file used by ExternalPrintServers by adding a required field 'id'. BUG=chromium:988489 TEST=tested on nautilus Change-Id: I2ab24170614163893a63c0604dabc4c17904e451 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1857566 Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Auto-Submit: Piotr Pawliczek <pawliczek@chromium.org> Cr-Commit-Position: refs/heads/master@{#706539}
-
Garrett Beaty authored
These changes simplify migrating to starlark by removing spurious diffs from the semantic diff. The names of the buckets have been switched to short names rather than long names of the form luci.<project>.<bucket>. These are treated equivalently by buildbucket, but lucicfg does not allow long bucket names. The category field is ignored by buildbucket, so the category field has been removed from the build definitions. Change-Id: If80a00385cb7a39539472295a51b7fd8713eaf55 Bug: 1011908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852411Reviewed-by:
-
Collin Baker authored
This also renames TabStripViewProxy to TabStripEmbedderProxy for consistency with TabStripUI::Embedder. Bug: 1005565 Change-Id: Id48d9fd8f946fb81d5d5e161a1cec85f97e6a426 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862120Reviewed-by:
John Lee <johntlee@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#706537}
-
Peter Boström authored
This has now been fully replaced with HighlightPathGenerator instances. Bug: chromium:1007546 Change-Id: Id163bd002143bc4b044dcd815abb5aa45d4e41c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864381Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#706536}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/520ed2286b88..ebe5dcf0d9ad git log 520ed2286b88..ebe5dcf0d9ad --date=short --no-merges --format='%ad %ae %s' 2019-10-16 tdusnoki@inf.u-szeged.hu Define getHostCPUFeatures for Windows on ARM64 platform Created with: gclient setdep -r src/third_party/swiftshader@ebe5dcf0d9ad 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 TBR=swiftshader-team+autoroll@google.com Bug: chromium:893460 Change-Id: I8ce09bf17bcc6f9166a5b680c12e054cce23722d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864561Reviewed-by:
-
Austin Eng authored
jsoncpp will be added as a DEP of Dawn to dump perf test output Bug: dawn:208 Change-Id: I0cfc3d9caebbcffb6ff68ecd98f6bd1ad4cbf873 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863356Reviewed-by:
-
Andrew Luo authored
See https://chromium.googlesource.com/chromium/src/+/HEAD/chrome/test/android/javatests/src/org/chromium/chrome/test/pagecontroller/README.md. Bug: 924194 Change-Id: I4ac12207fcd54125f5741021a9450c6c061bfbf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838306 Commit-Queue: Andrew Luo <aluo@chromium.org> Reviewed-by:
Sky Malice <skym@chromium.org> Reviewed-by:
-
Manu Cornet authored
Bug: 1009550 Change-Id: Ifb3ba316dfd1c6bbb48a9e3c3d2a7efec6d5a630 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864609Reviewed-by:
Matthew Mourgos <mmourgos@chromium.org> Commit-Queue: Manu Cornet <manucornet@chromium.org> Cr-Commit-Position: refs/heads/master@{#706532}
-
Mason Freed authored
Prior to this CL, the root damage rect might have partially intersected child render passes that had backdrop filters applied. In that case, the backdrop filter code would attempt to read back the backdrop image, and would find already-filtered content outside of the damage rect, but inside the render pass quad bounds. It would then filter this image, and if the backdrop filters moved pixels, some of that double-filtered content would bleed back into the damage rect and be used. This would lead to visual artifacts. With this CL, any child render passes that contain pixel-moving backdrop filters are checked for intersection with the root damage rect, and if they intersect, the damage rect is expanded to include the entire child render pass output rect. Bug: 986206 Change-Id: I81a51e24548cae736172938ce190f6ba4c6d2b94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847675 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by:
Eric Karl <ericrk@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#706531}
-
Bruce Long authored
Per suggestion in discussion in https://crbug.com/983683, the method SyncRendererPrefs() now calls WebContentsImpl::SendPageMessage to broadcast renderer preferences changes, going through RenderFrameHostManager to send the IPC to all processes involved in a page (via RenderFrameProxyHosts in the main frame). SyncRendererPrefs was also moved to from RenderViewHostImpl to WebContentsImpl where it more logically belongs. New test coverage is added (WebContentsImplBrowserTest.SyncRendererPrefs), which fails without the fix in this change because the SetRendererPrefs IPC is never sent from the render process hosts associated with subframes. Bug: 983683 Change-Id: I70ad24b5f7a8537edfbe40db239522f13f5388b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1857398Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Bruce Long <brlong@microsoft.com> Cr-Commit-Position: refs/heads/master@{#706530}
-
Dmitry Gozman authored
This change moves DispatchDidStartProvisionalLoad, call_before_attaching_new_document, DidCreateNewDocument and DispatchDidCommitLoad to a single place in FrameLoader::CommitNavigation. The only behavior change is that DidStartProvisionalLoad now happens after commit. This makes it possible to combine all of these callbacks, greatly simplifying contract between WebLocalFrame and WebLocalFrameClient. We can also create provisional document loader after detaching previous document, which will make the commit sequence simpler. This corresponds to the step 7.d from the doc linked to the bug. Bug: 855189, 555773 Change-Id: I0b99ca33754fc22427c20cc9948a5bab571c2f40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1818718 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#706529}
-
Himanshu Jaju authored
GetDeviceCandidates + RenameDevices had become a bit complicated to understand. Also, the number of calls to GetDeviceName has been halved (at most once per device). Bug: 1014107 Change-Id: I1f5a04f63cef1b3e94b719fc376ae4d47cfbf516 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865173 Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#706528}
-
Yuki Shiino authored
Makes SymbolNode's constructor easy to call. It turned out that most callers will pass simple template text. Bug: 839389 Change-Id: Id27031efbbb5b216866c38a62fb805349652b380 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862596 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#706527}
-
Daniel Hosseinian authored
Change-Id: I8f99b6ac598d280780b1569c1deabb512312b4b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860284 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
-
Xiaoqian Dai authored
If after drag ends, we should go to home launcher screen, do the window scale down and opacity fade out animation. The window will scale down to the middle of the display and disappear. During the window scale down animation, the backdrop should be disabled. Also fixed an issue that if the drag is cancelled, overview should be dismissed if it was opened during dragging. Bug: 997885 Change-Id: I6a27c8e4bf9021e14ed0d26260c89c97adec614b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863256 Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
-
Aran Gilman authored
Enabling the flag appears to break rendering of most pages on ChromeOS, including chrome://flags. This CL removes the option to enable it for now. Bug: 1011696 Change-Id: I818be2add7c34e181297477244805e02f7ffcb85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1848478Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Aran Gilman <gilmanmh@google.com> Cr-Commit-Position: refs/heads/master@{#706524}
-
Olivier Li authored
This is ground work for moving ProfileSyncService to the ThreadPool (see bug) but also a logical change by itself since these functions have no specific need to be run on a dedicated thread. Change-Id: I45bdbeb0a768af838700a37945613c1ddc475ea0 Bug: 1014464 Change-Id: I45bdbeb0a768af838700a37945613c1ddc475ea0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862666Reviewed-by:
-
Aga Wronska authored
The feature is enabled since February and no problems were reported. Bug: 1013650 Change-Id: Iec095972123022e2b0d0e0a116a373c99daaeee4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1856629Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Commit-Queue: Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#706522}
-
zhaoyangli authored
Moved ensureAppLaunchedWithFeatures from -setUp to overriding launchAppForTestMethod to eliminate unnecessary relaunches. CQ bot run results show significant improvement without the relaunches. BUG: 1009017, 1010463 Change-Id: I650304daaa9e4271310e180635a8fb6ff865f717 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854786Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#706521}
-
John Budorick authored
Bug: 1014754 Change-Id: I0e3e24f8c43d9835937f47e95ece0ca9f3efd82f Tbr: bsheedy@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864375Reviewed-by:
-
Daniel Hosseinian authored
Change "Fit to page" string to "Fit to printable area." "Fit to paper" will center and scale the page contents of a PDF to fit the borders of the paper being printed on. In contrast, "fit to printable area" will center and scale the page contents of a PDF to fit within the margins of the printer's printable area. Bug: 989978 Change-Id: I5caf319959fb8d9bd32f3c78c86a27379cffe166 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1812129 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#706519}
-
Yuki Shiino authored
LiteralNode is a literal text, not a template text, so the template rendering engine will output the text as is without applying any template magic. Bug: 839389 Change-Id: Ie1c83e442ba68ff242854f491b0d042ad940b73c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864753Reviewed-by:
-
Elly Fong-Jones authored
While the Ok/Cancel messages appear to be dynamically computed, in fact this dialog never calls DialogModelChanged, so the initial messages are always the ones used. As such, this change will cause no behavior difference. Bug: 1011446 Change-Id: Ib23484c83eaa8c64b8e5062d922b0365b4e65d66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1854684Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#706517}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/45deba856dba..2f8a97068d48 git log 45deba856dba..2f8a97068d48 --date=short --no-merges --format='%ad %ae %s' 2019-10-16 taylori@google.com Merge "perfetto-ui: Go to thread state" 2019-10-16 taylori@google.com Merge "perfetto-ui: Move details panel into it's own component" 2019-10-16 fmayer@google.com Merge "Set correct fields on fist packet in sequence." 2019-10-16 tneda@google.com Merge "perfetto-ui: Show heap profile track even if the trace has only heap profiles inside" 2019-10-16 zakerinasab@google.com Merge "Fix minor issue in setting arg id" 2019-10-16 lalitm@google.com Merge "trace_processor: fix dcheck failure when we get an out of order upid counter" 2019-10-16 fmayer@google.com Merge "Fix incorrect comment." 2019-10-16 lalitm@google.com Merge "trace_processor: fix support for optional<stringid> columns" 2019-10-16 eseckler@google.com Merge "Revert "processor: Move TimestampedTracePiece into its own header"" 2019-10-16 lalitm@google.com Merge "trace_processor: add support for remaining operations on new tables" 2019-10-16 eseckler@google.com Merge "processor: Move TimestampedTracePiece into its own header" 2019-10-16 eseckler@google.com Merge "processor: Import and export legacy flow event args for all TrackEvents" 2019-10-16 tneda@google.com Merge "perfetto-ui: Fixing SQL error for ambiguous name" 2019-10-16 tneda@google.com Merge "New track with flamegraph for heap profiles" Created with: gclient setdep -r src/third_party/perfetto@2f8a97068d48 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 TBR=perfetto-bugs@google.com Bug: None Change-Id: I8a168ac61ce0bcb5f8b210fc92301209a14032f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864646Reviewed-by:
-
