- 30 Jul, 2019 40 commits
-
-
Chase Phillips authored
As part of cleanup from CL https://crrev.com/c/1626660, this CL moves creation of CursorImpl into IndexedDBDispatcherHost by refactoring AddCursorBinding into CreateCursorBinding. As a result, the OpenCursor calling path no longer needs to pass the origin and sequenced task runner into the OpenCursorOperation task and ownership of CursorImpl and the mojo binding steps is made simpler. Bug: 988868 Change-Id: Iab0be1d24d98fc6b0088d01c67c1b778c5c13318 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725318Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Chase Phillips <cmp@chromium.org> Cr-Commit-Position: refs/heads/master@{#682428}
-
Mounir Lamouri authored
Bug: None Change-Id: I0e37df2a199df5cd5e6a3bd42270383133638a62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726653Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#682427}
-
Henrique Nakashima authored
BEST_EFFORT does not work in background (crbug.com/988604). Bug: 988604, 984559 Change-Id: I99f3793d9bb949570cd78c9f969b05fea138aed7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726870 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#682426}
-
Tibor Goldschwendt authored
Bug: 955494 Change-Id: I01bd565e37f354e1ddb7ba74a318ede9a3a7ed9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717779 Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#682425}
-
Mounir Lamouri authored
Bug: None Change-Id: Id05cede1d4cf7f8ff3202c531575868c8b56265b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726934Reviewed-by:
-
Ian Kilpatrick authored
A cleanup of the cleanup! Upon further inspection the node parameter isn't strictly needed anymore. This has one slight behaviour change, which I think was incorrect: flexItem.computedStyleMap().get('min-height') == 0px now. This is more correct I believe as computedStyleMap should act as if a box isn't attached, which is the same behaviour if elem wasn't attached to the document. Change-Id: I4522d1f591cdfe7ec88522f6da49be599d2db4ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716089 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:Xida Chen <xidachen@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#682423}
-
Michael Achenbach authored
This is a no-op on iOS, since there the system or recipe side sdk is used. Bug: chromium:986701 Change-Id: I1daffa748b0dadd074a9c8ca2b756416c197ca1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725914Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#682422}
-
Ian Prest authored
This change sets the kPreviousOnLineId and kNextOnLineId attributes on PDF content if two text runs are determined to be on the same line. This is determined using a threshold, similar to the current paragraph detection. Any delta-y greater than 1.2x the median line spacing is considered a new paragraph (unchanged), and now any delta-y greater than 0.8x the median line spacing is considered a new line. Bug: 985604 Change-Id: If821bb6e5faadf244417f083d439a9460157f48e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709808Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Kevin Babbitt <kbabbitt@microsoft.com> Commit-Queue: Ian Prest <iapres@microsoft.com> Cr-Commit-Position: refs/heads/master@{#682421}
-
Ionel Popescu authored
This CL includes the following changes: - calendar_picker_refresh.css was added as a way to extend the current style used for date popup - calendarPicker.js was changed: - to support different sizes for cells - to provide different icons for forward, back month buttons - todayButton was moved to a different position - locale_win | icu | mac to change the label used for weekdays to the shortest one provided by each platform Added tests to validate the new UI for input type="date". Although the current change affects other types (datetime-local, week, month) this change is the first of a series of changes which will update the popup UI for all these types and tests will be added for each type. Bug: 988155 Change-Id: Ibfbddd9f523f4adad79b6af2520989c3980bc18c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721842 Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Reviewed-by:Mason Freed <masonfreed@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#682420}
-
Ren-Pei Zeng authored
This CL extends MJDA interface to support DMA-buf backed VideoFrame with pixel format not limited to I420, and focuses on the implementation in VAAPI backend. In the VA pipeline, the input JPEG image is first decoded into an internal VASurface, and then Video Processing Pipeline (VPP) is used to convert it into target VASurface, which is imported from client's VideoFrame. For cases VPP doesn't support the conversion, it fallbacks to get VAImage from decoded surface and do software conversion. The pixel formats supported by VPP can be queried by vaQuerySurfaceAttribs(), but the internal surface format from a JPEG decoding is hidden and may not be supported (e.g., Mesa driver's VPP doesn't support conversion from a decoded 4:2:2 JPEG). To work around this, VaapiWrapper::IsJpegDecodeVppSupportedSurfaceFourCC() is deduced from some observations to filter unsupported cases. V4L2 backend is not implemented in this CL. It will return error if the output frame given is backed by DMA-bufs. The JDA unittest is extended to test with DMA-buf and shared memory output buffers. CQ-DEPEND=CL:1645712 Bug: b:120057531 Test: jpeg_decode_accelerator_unittest Change-Id: I5a9a46f7b7e9b142c7dfbf59acd0125f90c70288 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558746Reviewed-by:
Ricky Liang <jcliang@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Commit-Queue: Ren-Pei Zeng <kamesan@chromium.org> Cr-Commit-Position: refs/heads/master@{#682419}
-
Daniel Rubery authored
A few Download metrics expired in M77, and we don't have any near-term plans for these metrics, so remove them. Bug: 975143 Change-Id: I63c480286e271c668c57bb7d65a8d2581ae278af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724867 Auto-Submit: Daniel Rubery <drubery@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#682418}
-
Sergey Ulanov authored
By default media demuxer buffers 150MB of video and 12MB of audio. This may be to much for some Fuchsia devices. Use low values of 30MB and 2MB. Bug: ZX-4768 Change-Id: I084f85dcc92fa54c56fd06ab8270f4fb73762410 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725240 Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#682417}
-
Scott Violet authored
Specifically Memory.Renderer.PrivateMemoryFootprint. This refactors existing code in hopes of sharing names and some portions of the logic. This doesn't include Memory.Browser as it's not really under our control (I'm starting an email thread on this one). Logging is only enabled for the non-single process case. This patch is exactly the same as the first patch. I fixed the reason that lead to the revert here: https://chromium-review.googlesource.com/c/chromium/src/+/1716584 BUG=981102 TEST=covered by integration tests TBR=bcwhite@chromium.org, changwan@chromium.org, chrisha@chromium.org Change-Id: Iabb1193481600c208fe56207aaef01d1fd3b9401 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726410Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#682416}
-
Mohsen Izadi authored
While adding a test to //ui/compositor/layer_unittes.cc, I noticed that there are a bunch of factory functions that return raw pointers that the call sites wrap in unique_ptr's. Changed them to return unique_ptr's to make ownership more clear. BUG=none Change-Id: I7f54855265fadc7692c7ca7e40937642ed809f00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726897Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#682415}
-
Philip Jägenstedt authored
The ones in the past that remain unfortunately still have deprecations referencing them, which should be fixed. This only makes it clearer. Change-Id: I7ec07fa5a1e543739851c59e0770b99fc121b908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724645 Auto-Submit: Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#682414}
-
John Abd-El-Malek authored
Bug: 934009, 791049 Change-Id: Id0fcc731e78511f3b8f54105b4fbfec5ccd8a06e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727029Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#682413}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/1157607f2f54..3b361d1e1281 git log 1157607f2f54..3b361d1e1281 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 jazbel@chromium.org usergroup_baseline: Expect cfm-monitor in video. Created with: gclient setdep -r src/third_party/chromite@3b361d1e1281 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I697e0cce45db5bd50a4bf1a397240bb4928e3a0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726890Reviewed-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@{#682412}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ia99207b6155c08bdc6f24e2f719501f4a7386c20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726293 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
-
Carlos IL authored
Mixed content autoupgrade experiment is still ongoing, so the histograms are still needed. Bug: 893647 Change-Id: I893d443c7b43970eb4d91124dd07c94541811ad5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726311 Auto-Submit: Carlos IL <carlosil@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
-
Ben Kelly authored
When we load the cache_storage index we try to determine if its fresh or stale by comparing its timestamp against the timestamp of the various simple disk_cache directories. Both cache_storage and simple disk_cache write their index files out using a delay. The cache_storage delay is 5 seconds and the simple disk_cache delay is 20 seconds. This means that the simple disk_cache index is always written last and as a result the cache_storage index is almost always considered stale. This CL fix this by extending the cache_storage delay to match the simple disk_cache delay. It also implements a shorter delay on android when in the background like simple disk_cache uses to avoid losing data when the app is killed by the operating system. Finally, the CL also now properly flushes the index to disk if there is a pending write when the cache_storage subsystem is torn down. Over time this should cause ServiceWorkerCache.UsedIndexFileSize to show more cases where the index file is used to provide the size. Bug: 988001 Change-Id: Idaa09b956edcfa9e70ac1fdb9b43adcd73ec0508 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721389 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/da76f1d1887d..cde7deb536fa Created with: gclient setdep -r src-internal@cde7deb536fa The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None,chromium:None Change-Id: I5b72f6d006aa9eae2f8d6b26bae3c56027454143 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726892Reviewed-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@{#682408}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/e73fe02a406e..2568b37b25f5 git log e73fe02a406e..2568b37b25f5 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 rmhasan@google.com [Telemetry] Create an IsLowEnd function for the AndroidPlatformBackend class Created with: gclient setdep -r src/third_party/catapult@2568b37b25f5 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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 TBR=simonhatch@google.com Bug: chromium:973936 Change-Id: I6bc51cc89472e9dca0c1808862c8ba8229fb50e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726809Reviewed-by:
-
John Abd-El-Malek authored
Bug: 934009 Change-Id: I0a70decdec255d4f635124751d9b1478662324ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726949 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Auto-Submit: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
-
Jian Li authored
This reverts commit 107a4e3e. Reason for revert: <INSERT REASONING HERE> ==20541==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x557884d1cbb9 in ClickToCallIconView::Update() ./../../chrome/browser/ui/views/sharing/click_to_call/click_to_call_icon_view.cc:80:7 https://ci.chromium.org/p/chromium/builders/ci/Linux%20MSan%20Tests/18323 The real issue indeed lies in click_to_call_icon_view.h Original change's description: > Integration tests for click to call > > Bug: 982229 > Change-Id: I3d0f19b55dc6dc07c6ad427d670aaa2db0a9af2d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1718410 > Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> > Reviewed-by: Peter Beverloo <peter@chromium.org> > Reviewed-by: Richard Knoll <knollr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#682242} TBR=peter@chromium.org,knollr@chromium.org,himanshujaju@chromium.org Change-Id: Ic56b5b5bd151f42992ba4bc8d9e13e73dd135983 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 982229 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727231Reviewed-by:
Jian Li <jianli@chromium.org> Commit-Queue: Jian Li <jianli@chromium.org> Cr-Commit-Position: refs/heads/master@{#682405}
-
Charlie Andrews authored
This class will contain the Android-specific unwinding implementation, which will rely on libunwindstack. libunwindstack will be pulled in as a dynamic feature module (DFM). Having a stub version of this class will allow us to create StackSamplerAndroid. (StackSamplerAndroid will need to create a StackSamplerImpl, which accepts an Unwinder as a constructor parameter.) TBR=gab@chromium.org R=wittman@chromium.org Bug: 988574 Change-Id: Id929731e94232f457add7914eb426ebcdb0bf0f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726829Reviewed-by:
Charlie Andrews <charliea@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#682404}
-
Wez authored
FIDL defines that only messages with a response should have a non-zero transaction Id set, and recent changes to FIDL C++ bindings actually verify & enforce that. Update the FIDL/JS generator to omit Ids from one-way messages. Bug: FIDL-764 Change-Id: I5ab6b94283fae2e67bb92a8f856e143f5d82a75f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726612 Auto-Submit: Wez <wez@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#682403}
-
Ben Pastene authored
Bug: 980748 Change-Id: I10965a3f20ca5ba8fdaabaeeda31bccd40c91ee7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726234 Auto-Submit: Ben Pastene <bpastene@chromium.org> Reviewed-by:
Vlad Tsyrklevich <vtsyrklevich@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#682402}
-
Luum Habtemariam authored
This change adds service startup logic based on the already landed kCrosVmCupsProxy feature flag, disabled by default. Bug: chromium:945409 Test: manually confirmed correct flag behavior Change-Id: I6198cfcf4011c557b09d74d33f241cc61629d4ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713237 Commit-Queue: Luum Habtemariam <luum@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Cr-Commit-Position: refs/heads/master@{#682401}
-
Erik Jensen authored
Previously, clipboard messages were capped at the default safe size of 64KiB. This patchset raises the limit when the session descriptor indicates that a larger size is supported. Bug: 988865 Change-Id: I651c4e0a5aa96b84950eb4fa8f798af7579eff85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726277 Commit-Queue: Erik Jensen <rkjnsn@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Auto-Submit: Erik Jensen <rkjnsn@chromium.org> Cr-Commit-Position: refs/heads/master@{#682400}
-
Xiyuan Xia authored
PepperTCPSocketMessageFilter could be released on IO thread with an outstanding |firewall_hole_| and indirectly calls dbus code on IO thread. The CL makes sure |firewall_hole_| is deleted on UI thread. Bug: 989072 Change-Id: I9266c21a96fa5b931f81d25bc6c8e91293a5e9a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726235Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#682399}
-
Sadrul Habib Chowdhury authored
BUG=790761 Change-Id: Id33e2f4362637bd5871b8d4e63a070b02dff8912 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724515Reviewed-by:
Simon Hatch <simonhatch@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#682398}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/11c60ffe..781babd0 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: Ie982a274c53c3ac4fbf116c9f601d0f99233493c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726432Reviewed-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@{#682397}
-
Lei Zhang authored
Change-Id: I5a1156b00535832bdbe186be8d8407c4e5c341e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726714Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#682396}
-
Yi Gu authored
This patch validates that whenever the kHitTestAsk bit gets set, the async_hit_test_reasons is also set and vice versa. Bug: 985786 Change-Id: I424053f3ed62eb3f65b4116de9630bd437b0e1d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710845 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#682395}
-
Kristi Park authored
Add the new NTP team owner (dbeam@), and remove the old team (jkrcal@). Change-Id: I56e4436091ff1e98d68a23afc61530442579e0b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723300Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#682394}
-
Clark DuVall authored
UIThreadExtensionFunction was merged into ExtensionFunction in http://crrev.com/c/1718990. This removes the stub UIThreadExtensionFunction class and renames all the references from UIThreadExtensionFunction to ExtensionFunction. This CL was generated with the command: git grep --name-only UIThreadExtensionFunction | \ xargs sed -i 's/UIThreadExtensionFunction/ExtensionFunction/g' Bug: 980774 Change-Id: Ie1772044041517b88e9f8a625a2b941913aae9b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721876Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#682393}
-
Adam Langley authored
The logic here is easier if the unsupported cases are rejected first. Change-Id: I231935618dea789972934e7cd09ec3616744b9e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725209Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#682392}
-
danakj authored
If a RenderWidget is started as hidden, it should generate a local surface Id when it's shown. On Webview, the delegated_frame_host_ is null, which was preventing this from happening. Change the conditional to still generate the local surface ID. We got by with this bug because RenderWidgets for RenderFrames are always started as visible, then hidden with a method call to the RenderWidgetHostView. Future CLs remove this ping-ponging of visibility states. R=boliu@chromium.org Bug: 419087, 745091 Change-Id: I7c7ffb49fde75c94b68ffb4e72b3a7676ac6d429 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726872Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#682391}
-
Ahmed Fakhry authored
The Files app, as well as other apps, if they're evicted due to being occluded by other windows, will show as empty for a second or more in overview until reloaded. This CL makes them behave the same way as browser windows, that is they show stale contents until reloaded. BUG=986085, 866622 TEST=Manually, follow steps on bug, and note the issue no longer shows. Change-Id: If9a2b26b914fe55672d15d4b560cbe6d7e996591 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1711843Reviewed-by:
kylechar <kylechar@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#682390}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/968d1d819bc0..d5acde64a3a5 git log 968d1d819bc0..d5acde64a3a5 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 lalitm@google.com trace_processor: rename NumericColumn -> NumericStorageColumn Created with: gclient setdep -r src/third_party/perfetto@d5acde64a3a5 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Bug: chromium:135177627 Change-Id: Ie3b3b183ac9aa648b2696c70cc99e15f0f9610e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726810Reviewed-by:
-
