GitLab

Also clean up some old owners who aren't active in the code anymore.

Change-Id: Ib809d30c30c3203cb9cad16c9c643c678602b961
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728447
Auto-Submit: Nathan Parker <nparker@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683007}

BUG=972848

Change-Id: I1965cbbc2b57db143e504a2bd8a233e6f7063248
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724902Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Commit-Queue: Julian Watson <juwa@google.com>
Cr-Commit-Position: refs/heads/master@{#683006}

PlatformSensorReaderWinrtLightSensor

As the third step for implementing usage of the
Windows.Devices.Sensors WinRT API in Chromium, this CL:
  - Implements PlatformSensorReaderWinrtBase, the base class
    used to implement all of the Windows.Devices.Sensors based
    PlatformSensorReaders.
  - Implements PlatformSensorReaderWinrtLightSensor, the derived
    class of PlatformSensorReaderWinrtBase which adds support
    for light sensors using Windows.Devices.Sensors.LightSensor.
There is heavy use of templates since the Windows.Devices.Sensors
API is strongly typed.

Verified functionally by:
  - Built chrome.exe.
  - Ran chrome.exe on laptop with light sensor.
  - Navigated to website that polls the W3C light sensor:
    - Verified light sensor could be polled with WinRT feature
      flag on and off.
  - Ran chrome.exe on laptop without light sensor.
  - Navigated to website that polls the W3C light sensor:
    - Verified the light sensor failed to instantiate with the
      WinRT feature flag on and off.
Also ran new PlatformSensorReaderTestWinrt unit tests.

Bug: 958266
Change-Id: Iaa69d92f9e7923099653b4f554efc2852162b53f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1703327
Commit-Queue: Wenjie Shi <wensh@microsoft.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683005}

This gets attached to the XRInputSourceDescription mojo struct
which is sent from XR device processes to blink.

For WMR controllers, use:
["windows-mixed-reality", "touchpad-thumbstick-controller"]

Populating this array for other platforms such as Oculus and OpenVR
will come in later CL(s).

Bug: 979250
Change-Id: I06c6666c4c085f6578630c25059d07faff158bbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726903
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683004}

This testing is gated on the phone-home capability of mac/ios, which makes
it difficult to test.  Removing test.

Bug: 989629
Change-Id: Idb870e9f7307b2f31d7ce3eab9202a5e0c8c4acf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729578
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683003}

Create() does not need to check IsSetPermittedInContext because
it is already checked when setting a cookie. It also does not have
to check for a secure scheme when creating a Secure cookie, because
that is checked when setting a cookie. Create() should only
need to check that the cookie it creates is canonical.

Bug: 989098
Change-Id: Ic5be164cfb60825c7775c3bc58986a835afa499e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726789
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683002}

Rename the api for setting custom backgrounds and add an additional
collection_id param. This will be used for the "daily refresh" feature
in https://crrev.com/c/1721841.

Bug: 850317
Change-Id: Ibf14af8db94b85dc489d0d24cb28af33495ff3b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717921Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683001}

This change adds an explicit ShowTouchToFill() API to the
PasswordManagerDriver and provides a stub implementation for
PasswordManagerClient.

Bug: 957532
Change-Id: I87a3d1b21caedfbf651c2294a4e10e8b4ac69e48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1702251
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Auto-Submit: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683000}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/364640e2491e..447b45d42307

git log 364640e2491e..447b45d42307 --date=short --no-merges --format='%ad %ae %s'
2019-07-31 smut@google.com [vpython] Roll to 98a268c6432f18aedd55d62b9621765316dc2a16

Created with:
  gclient setdep -r src/third_party/depot_tools@447b45d42307

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-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=agable@chromium.org

Bug: chromium:898348
Change-Id: Id6f1378c96f5ca5490510d139d95f6757271508f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729839Reviewed-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@{#682999}

- Have run Leak Sanitizer in Local machine and not seeing
memory leak from IconStore anymore.
- Add unit test for all APIs.

Bug: 961073, 963290
Change-Id: I70810b83616c89663ec8a0d4ed86d6ee8ee42d80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726659
Commit-Queue: Hesen Zhang <hesen@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682998}

Bug: 934009
Change-Id: I0aa4561293f69d4db3ea677dfb2fd952770a8f64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730129
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Auto-Submit: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682997}

On high-dpi screens, when running under software_renderer, the
backdrop filter clip rect was not properly scaled, which made
the filtered effect get incorrectly cropped.

Bug: 985968
Change-Id: Ie9dae15bf710e87ecfc584d23fd979929fada579
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725252
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682996}

This adds the change to enable/disable heursitic stylus/palm rejection
as a visible flag in chrome://settings. Allows folks to turn it on/off
as needed, and mentions (in the visible description) it is not
intended for all devices.

Bug: 982118
Change-Id: Id9c18eb5b5c7bec359a0a650acf4a14fb2303120
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728449
Commit-Queue: Rob Schonberger <robsc@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682995}

While refactoring the BufferQueue (crrev.com/c/1636450) to get rid
of GL dependencies we replaced CopyTexSubImage2D with
CopySubTextureCHROMIUM.

Turns out that CopySubTextureCHROMIUM seems to be off by one pixel
in some cases/on some platform.
This caused glitches for partial swap.

The main problem seems to be using mediump as precision for float
even if highp is available.

This CL fixes that.

Tests will follow up: crrev.com/c/1727650

Bug: b/137245499, 987276
Test: deploy on elm, UI is not "shaking"
Change-Id: I22c2c936dc826949a9ad21abac577a1dec5598c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727651Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682994}

SendTabToSelfBubbleDeviceButton is owned by Views once added to the
Views tree.

BUG=985990

Change-Id: I641124d31eb69a17ce0764f50220dbb2f9b9287c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728442Reviewed-by: Jeffrey Cohen <jeffreycohen@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682993}

Bug: 989723
TBR: cmp@chromium.org
Change-Id: Ib5f4b3fb5e6821b87c67d302993ce8987ef7a468
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730135Reviewed-by: Sky Malice <skym@chromium.org>
Reviewed-by: Chase Phillips <cmp@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682992}

Focus gain causes virtual keyboard to show. Then virtual keyboard takes
the bottom inset and causes the window and view size to shrink, on
chrome and sometimes on webview.
At this point, the bottom inset may occlude the input form,
i.e. the input form is behind the keyboard and is not visible.

We have the following auto-scrolling logic to mitigate the inconvenience
here:
1) Check the size of visible display size after showing keyboard.
2) Wait for the view height change after showing keyboard.
3) Change the viewport size
4) Scroll focused editable node into view.

In the browser, this is in order. However, in the renderer, the order
of 3) and 4) sometimes gets reversed.
I suspect that this happens because the two messages are going through
different IPC channels.

Now we do the following:
1) Wait until SynchronizeVisualProperties() changes visual viewport.
2) Detect that blink's scrollable viewport size has changed
3) Comfirm this signal against the visible display size
4) Scroll focused editable node into view

This also adds some test and refactors ImeAdapterImpl.

Bug: 920061

Change-Id: Id237fa76c304c92b5459bda4fe6591c96cb804d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562585Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682991}

Per UX's word, kGoogle*Dark* should be removed or replaced as they are
old colors that we're not using anymore.
This cl goes to replace kGoogleRedDark600 in ash/system/* with
kGoogleRed300 while the background is dark.

Bug: 986911
Change-Id: I0c6c6a1ac3598e854c45e018c87e9bbc21256f94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729240Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Min Chen <minch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682990}

Remove the dynamic linking of SHGetStockIconInfo as the project no longer
supports Windows XP where this was necessary.

Bug: 986625
Change-Id: I89abb16f8089fc475a9930f4f9ea4ad4ea1a71fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726765Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682989}

MessageLoopForUI will go away, eventually.

ScopedTaskEnvironment will per default start a ThreadPool, which should
be fine in most of the cases. If you believe your test needs to make sure
that no ThreadPool runs let me know and I will update the patch.

BUG=891670
This CL was uploaded by git cl split.

R=kpschoedel@chromium.org

Change-Id: I5b0c11c1c4d51400694238fb286d265d9c9e0d5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715300Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Auto-Submit: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#682988}

Fix missing include for DWORD_PTR on WIN

Change-Id: I2cc06190fa6ea9cca944a2198c95e2b56886f1f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729634
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#682987}

This CL renames *_struct_traits.* to *_mojom_traits.* in
//components/content_capture.

*_struct_traits.* => *_mojom_traits.*

Bug: 806965
Change-Id: I22a27a70660e9e0c7ea685ddc44aaad0092a0040
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728536Reviewed-by: Tao Bai <michaelbai@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/master@{#682986}

Bug: 936114
Change-Id: Iec30e618b1361546d420dc36317bea8a9a3dd39d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728052
Auto-Submit: John Budorick <jbudorick@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682985}

Bug: 984173
Change-Id: I34a93ba8b456cd2bf49270f55dfa00297a547168
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728185Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682984}

https://webrtc.googlesource.com/src.git/+log/8d3e4bd9a6c5..add7ef974ee2

git log 8d3e4bd9a6c5..add7ef974ee2 --date=short --no-merges --format='%ad %ae %s'
2019-07-31 steveanton@webrtc.org Sanitize the codec list before sending it to the media engine
2019-07-31 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 6ba1e902..1bdd7918 (682701:682806)

Created with:
  gclient setdep -r src/third_party/webrtc@add7ef974ee2

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:987598,chromium:None
Change-Id: Iee06110bb188a1a97da12aea3c59baea47c739f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729840Reviewed-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@{#682983}

This CL renames *_struct_traits.* to *_mojom_traits.* in
//components/content_settings.

*_struct_traits.* => *_mojom_traits.*

Bug: 806965
Change-Id: I35cd4278ff10e95c7b62bcf38c4881f4b22aaee1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728891Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/master@{#682982}

the input predictor.

Predicted events are made at a fixed time interval of 8ms. This
creates inconsistency in cases when the time interval between real
events is different from 8ms.

Change-Id: I7f99025f6a32ae8e43a4bfe8bbfe8f3e8a88c2bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1693807Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ella Ge <eirage@chromium.org>
Commit-Queue: Luis Sanchez Padilla <lusanpad@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#682981}

This patch updates the CrOS orderfile name to point to the newest
orderfile. Manual CL update for once, as in the future, it will
be done with an autoroller.

BUG=chromium:950627
TEST=The orderfile is tested on Chrome OS. No code is using the orderfile for now

Change-Id: If7113b9cdc1ac1c00ebb7aef91d2ded212564836
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729962Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Tiancong Wang <tcwang@google.com>
Cr-Commit-Position: refs/heads/master@{#682980}

https://pdfium.googlesource.com/pdfium.git/+log/a9d33bd8b6ba..033c7fb180fb

git log a9d33bd8b6ba..033c7fb180fb --date=short --no-merges --format='%ad %ae %s'
2019-07-31 tsepez@chromium.org Move fontglobal and fxcodec initialization to cpdf_pagemodule.cpp.
2019-07-31 tsepez@chromium.org Move the UNSUPPORT_INFO interface out of CPDF_ModuleMgr.
2019-07-31 nigi@chromium.org [SkiaPaths] Fixed missing texts.
2019-07-31 thestig@chromium.org Remove SkASSERT() usage in PDFium.
2019-07-31 tsepez@chromium.org Remove FSDK_ prefix from FSDK_SetSandBoxPolicy/FSDK_IsSandBoxPolicyEnabled.
2019-07-31 tsepez@chromium.org Break direct top-level fpdfapi to cmaps dependence.

Created with:
  gclient setdep -r src/third_party/pdfium@033c7fb180fb

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=pdfium-deps-rolls@chromium.org

Bug: None
Change-Id: Ie5ba3daef0b758c3380174f4c6180f31c7f772ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729841Reviewed-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@{#682979}

Turns the bounds renderer more red than green since the background on
the room-scale test page is also green, thereby giving a clearer color
change to validate the bounds.

Also adds controllers to the room-scale page so that height and tracking
can be validated.

Bug: 909933
Change-Id: Iccdc07aa9f70db71f6626f4c245160882d8b48d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729568Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682978}

It has been temporarily disabled within r666174.

BUG=973430

Change-Id: I747e166f1c6dcba478da897d0c661c5bb6cf2371
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726661Reviewed-by: Mike Wittman <wittman@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682977}

Adding cut, copy, and paste methods to text_input_manager in Switch
Access using synthetic key events. Set up Switch Access menu to call
these functions on press of cut, copy, and paste buttons.


Bug: 982004
Change-Id: Ifc85fb939cb1dbe8f4f3e407d20b931a0ad8c159
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727242Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Commit-Queue: Rose Garcia <rosalindag@google.com>
Cr-Commit-Position: refs/heads/master@{#682976}

Change-Id: I7681ca1295bb02b61bc3eb402b2122aa8769cff5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717778
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682975}

While looking at adding iframe support, I deliberately broke the check
in Blink and it wasn't obvious that any test broke. Therefore add some
tests for the current iframe behaviour before I start changing it.

Change-Id: Ia092e89bf35ca42d8ef3becd72fdaeb2ec43f8b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725210
Commit-Queue: Adam Langley <agl@chromium.org>
Reviewed-by: Nina Satragno <nsatragno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682974}

The focus outline is cut off top/left by the div boundaries due to
overflow-y. Fix this by adding 5px padding top/left. Note that this will
increase the height of the container by 5px (only visible when
scrolling), which is an acceptable trade off.

Bug: 989671
Change-Id: If0100f939bb030222778160c81d47da3df3163cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729955Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Kristi Park <kristipark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682973}

https://swiftshader.googlesource.com/SwiftShader.git/+log/324bdfed0692..27e2873765fa

git log 324bdfed0692..27e2873765fa --date=short --no-merges --format='%ad %ae %s'
2019-07-31 capn@google.com Fix Visual Studio solution build

Created with:
  gclient setdep -r src/third_party/swiftshader@27e2873765fa

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@google.com

Bug: chromium:b/123642959
Change-Id: I8d2aff0536d84d34e708c1f72e35e144facf12b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730035Reviewed-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@{#682972}

Accessibility metrics are fired once, 45 seconds after startup.
However, UMA counts unique users on a daily basis.

This means that the metrics system is only counting 1/2 of users who don't
relaunch their browser in a 2 day period. Or 1/3 of users who don't
relaunch for 3 days, etc.

Adding the following *.EveryReport alternate histogram names for
histograms that fire more often. These can be used with the unique
users aggregation option when viewing metrics:
Accessibility.CrosSpokenFeedback.EveryReport
Accessibility.Android.ScreenReader.EveryReport,
Accessibility.Mac.ScreenReader.EveryReport,
Accessibility.WinScreenReader2.EveryReport,
Accessibility.WinJAWS.EveryReport
Accessibility.WinNVDA.EveryReport
Accessibility.WinZoomText.EveryReport

Bug: 988502
Change-Id: I0b29dc35615668aafb7e873e574c1ba7ae280ead
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724698
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682971}

This CL removes the dynamic linking of SetProcessDEPPolicy as we don't
support < Vista.

Bug: 986625
Change-Id: Ie3e829150444db914d05798f8a67700439281934
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729961Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682970}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/18ea66a25d54..deb26d22f8ca

git log 18ea66a25d54..deb26d22f8ca --date=short --no-merges --format='%ad %ae %s'
2019-07-31 yueherngl@google.com bubs: Add board and paladin
2019-07-31 miahsanchez@google.com deploy_chrome: set the security context

Created with:
  gclient setdep -r src/third_party/chromite@deb26d22f8ca

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: Ie0c693ad8bc18908f368ee3d87711db71a58acb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729838Reviewed-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@{#682969}

https://android.googlesource.com/platform/external/perfetto.git/+log/9b95da7f782d..e02102755a5b

git log 9b95da7f782d..e02102755a5b --date=short --no-merges --format='%ad %ae %s'
2019-07-31 treehugger-gerrit@google.com Merge "Fix a spurious error from TracingMuxerImpl"

Created with:
  gclient setdep -r src/third_party/perfetto@e02102755a5b

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: None
Change-Id: If535c35883324635bf40f38e2172922162ea84b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729515Reviewed-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@{#682968}