GitLab

BUG=N/A
TEST=N/A

Change-Id: Id28dc53a9265fba56f1cd1b9a6879a1208b55ff1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036650Reviewed-by: J Kardatzke <jkardatzke@chromium.org>
Reviewed-by: Ian Barkley-Yeung <iby@chromium.org>
Commit-Queue: Miriam Zimmerman <mutexlox@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737932}

Refactored AXTree::PopulateOrderedSetItems, which is used for computing
set size and position in set, to make it more straight forward.
I made no change in the actual algorithm.

This change is needed to prepare for various tasks for exposing PosInSet
and SetSize for various elements

Change-Id: I2d4883bd5e3132ebbed721abb547bc24f5be0f10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020544Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Victor Fei <vicfei@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#737931}

Register it in ChromePreferenceKeys and use SharedPreferencesManager
consistently instead of SharedPreferences direct

Bug: 1022108
Change-Id: I5bd6ce1ac802ff3a77e2173fdaf51226ee89702d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033629Reviewed-by: Peter Conn <peconn@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737930}

This CL increases margin between the tiel and RHS icon in
preview tab.

Bug: 1047890
Change-Id: I96fcbd68b25a467c13a525d94c17976184812959
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032699Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737929}

This reverts commit 359bdf76.

Reason for revert: Proguard removes fragments in release mode

Original change's description:
> [Settings Refactor] Move autofill settings
> 
> Move autofill settings alongside autofill code.
> 
> Bug: 1047357
> Change-Id: Id5679d4392e23cff775dfcefa41930af9ab0f602
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031538
> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
> Reviewed-by: Theresa  <twellington@chromium.org>
> Commit-Queue: Natalie Chouinard <chouinard@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#737874}

TBR=rouslan@chromium.org,twellington@chromium.org,chouinard@chromium.org

Change-Id: I56bcf1ea3cdb276ee18d242ab858531f8081d673
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1047357
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036635Reviewed-by: Natalie Chouinard <chouinard@chromium.org>
Commit-Queue: Natalie Chouinard <chouinard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737928}

When the surface is not in current frame, but was in previous we set
buffer for it to nullptr to get release fences. Sometimes it leads to
flickering black. This CL sets visibility for those surfaces to fix it.

Bug: 1046792
Change-Id: I5b1324e2dd9f217724a3980181ccd42aba2e4098
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035299Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737927}

Bug: 1048256
Change-Id: I5ae4d08216fb0b7cbce03efa692252a755ffd307
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036557
Auto-Submit: Eugene But <eugenebut@chromium.org>
Reviewed-by: John Wu <jzw@chromium.org>
Commit-Queue: John Wu <jzw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737926}

This CL changes WebLayer to use the //components/security_interstitials
SSLErrorHandler that is used by //chrome rather than the custom fork
that it has been using to date. As part of this change,
WebLayerSecurityBlockingPageFactory is augmented to create the blocking
page types that were not necessary before (as they were never created
in the fork).

With this change, WebLayer now shares the core logic for determining
which interstitial to show on SSL errors with Chrome.

Bug: 1030692
Change-Id: Ibd1dadb9d03937cf578fd785ae4b32c943283749
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028068
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737925}

This change potentially has some privacy implications, but the
relevant people agreed it's not a problem and doesn't require a formal
review.  My original email asking if I need a review is included
below:

I have a very small Chrome change I'd like to land that might be
considered privacy-sensitive, but it's so small I'm not sure a full
review is warranted.

The change I want to make is to the desktop picker dialog that appears
when you use the "Cast..." feature to project your desktop to another
device. Currently, when you choose the "Cast desktop" option and click
a device to cast to, a dialog appears asking what you'd like to
share. In the typical usage of this dialog, the user can choose the
whole screen (or potentially one of multiple screens), or an
application window. In the case of casting, on every platform except
Linux, the only option is to cast a screen, and in the typical case
where the user only has a single screen, the dialog feels like an
unnecessary step in what is already a multi-step process, so I'd like
to bypass it entirely in that case.

The privacy concern is that even when there is only one option for the
user to pick, the dialog still serves the purpose of making the user
aware they're about to share the contents of their screen and gives
them a chance to prevent it from happening. This seems like a genuine
concern in the original use case of the dialog, which can be opened
from third-party JavaScript code through the
chrome.desktopCapture.chooseDesktopMedia function and used to send the
resulting video stream to an arbitrary destination. In the case of
casting, the dialog is opened by C++ code in Chrome itself only after
the user has gone through the following steps:

- Open the Cast dialog, either from the right-click menu, the Cast
  icon in the toolbar, or a Cast icon embedded in a page that uses the
  Cast API.

- Click the "Sources" button at the bottom of the dialog.

- Choose "Cast desktop" from the menu.

- Click on a Cast receiver (e.g. a Chromecast on the LAN) in the Cast
  dialog.

This, to me, seems like more than enough to ensure that a user really
does intend to broadcast their screen, and the final two steps of
clicking a thumbnail of the screen and then clicking "Share" are
entirely redundant.

Finally, there are a few points I'd like to clarify. First, I only
want to expose the ability to bypass the dialog to native code, not
the JavaScript API. The current version of the Cast dialog invokes the
desktop picker from JavaScript code, but we're moving to an all-native
implementation. Second, even though the Cast dialog can be opened from
third-party code embedded in a web site, if the user chooses "Cast
desktop" from the dialog, nothing that happens afterward involves any
third-party code. (That seems pretty confusing from a UX standpoint,
but harmless w.r.t. privacy.) Finally, I only want to bypass the
dialog in the case where the user only has a single screen, so there's
no possible confusion about which screen will be shared.

Bug: 637643
Change-Id: I07784aacd0e0fa6b4ea35378535e1e237fb8c57e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032088Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Commit-Queue: John Williams <jrw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737924}

This CL makes all call sites explicitly indicate which scans are allowed
to be performed.

Change-Id: I5f0211594de3d48b8c45f15f260461f298088bc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032016
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737923}

Before this CL, when a device had an end of life (EOL) date set,
we would show a message in the future tense telling the user when
the EOL date would occur. This was confusing if the device had
already passed the EOL date, since that date should have been in
the past tense. This CL adds a new, past-tense string and
displays it when appropriate.

Fixed: 1045687
Change-Id: I09c17a00a2c67fda505feabd30d216a09e5e25e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033342Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Cr-Commit-Position: refs/heads/master@{#737922}

https://android.googlesource.com/platform/external/perfetto.git/+log/78f5b92a0b6b..6da434932c2e

git log 78f5b92a0b6b..6da434932c2e --date=short --first-parent --format='%ad %ae %s'
2020-02-03 lalitm@google.com Merge "tp: make sql value accessors const"
2020-02-03 treehugger-gerrit@google.com Merge "processor: Allow fallback to tid/pid_overrides for new-style TrackEvents"

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

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

Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I9f884db17da20abbcf54130a42db553fb12de4c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036340Reviewed-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@{#737921}

Simplify the resizing logic. We're only supposed to be resized by the
embedder, so only resize when we're told to.

This way we no longer need to worry about the case when a WebContents is
embedded inside another WebContents as there's no size updates on the main
one.

Bug: b/147376354 b/148398442
Test: Verified resizes are applied to the EXO surface.
Change-Id: I70d2578bfe91018680b052af3dccf698c5303c72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032201Reviewed-by: Albert Chaulk <achaulk@chromium.org>
Commit-Queue: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737920}

Sets the height of the arrow button to match the bounds of the other
shelf buttons to place the tooltip at the same height.

Bug: 1043009
Change-Id: I7c83a825c41a5378eefc520023dcc25e6e25de64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033821Reviewed-by: Andrew Xu <andrewxu@chromium.org>
Reviewed-by: Manu Cornet <manucornet@chromium.org>
Commit-Queue: Ana Salazar <anasalazar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737919}

This reverts commit 50cf1bfe.

Reason for revert: give people time to update

Original change's description:
> Require the 10.15 SDK to build Chromium.
> 
> BUG=1023913
> 
> Change-Id: Ibd15e2c76413639c0caf8d1d255add07a815bcdf
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033986
> Auto-Submit: Avi Drissman <avi@chromium.org>
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Commit-Queue: Avi Drissman <avi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#737904}

TBR=avi@chromium.org,rsesek@chromium.org

Change-Id: I38a384dcec4cfca06a4de27e20a9c52d78e5dfea
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1023913
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036378Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737918}

This reverts commit 2a99fe61.

Reason for revert: going to give people some leeway

Original change's description:
> Update documentation for requiring the 10.15 SDK.
> 
> BUG=1023913
> 
> Change-Id: Ib92e5904843229f4e4d1d1fb2cdfa12cfb8db54f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032077
> Auto-Submit: Avi Drissman <avi@chromium.org>
> Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
> Commit-Queue: Avi Drissman <avi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#737908}

TBR=ellyjones@chromium.org,avi@chromium.org

Change-Id: I647d4d86ed348608251f5b3b3d2fb07bb43040a3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1023913
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036633Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737917}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/522a6a0e..43c981c9

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

Change-Id: I1a7c3150565a92624a6b4042b5cee296fbb1486c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035067Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Andrew Luo <aluo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737915}

SplitSettingsSync will allow the user to opt-out of browser sync.
However, IdentityAccessor::GetPrimaryAccountInfo() assumes the user has
consented to browser sync. The usage in AccountManager code isn't
related to browser sync consent.

Switch to using the "unconsented" primary account. On Chrome OS this
account always exists for the logged-in user account, whether or not
the user consented to browser sync.

See go/cros-sync-mock and go/cros-primary-account for details.

  on enrolled device, see screen/v3dTEPoVGyg

Bug: 1042400
Test: updated existing browser_test
Test: Account manager WebUI shows correct domain for primary account
Change-Id: Ied51c6aec99b34436a8c308a1ab0d2a569e00a9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031642
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Auto-Submit: James Cook <jamescook@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737914}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/db9ce1e03ccc..ba64534cd9d9


Created with:
  gclient setdep -r src-internal@ba64534cd9d9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1045987
Tbr: jbudorick@google.com
Change-Id: Iea79598ca0d1dfed62de797f1f0ee1bf4e5455c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036339Reviewed-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@{#737913}

This CL copies strings used by the OS Reset page from browser settings
to OS settings, and removes strings unused the browser settings.

Bug: 967888
Change-Id: I0ab9db7d0380748c4439453277df53de7e6f9a94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029265
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737912}

* Use temps for some minor repeated expressions, whose calculation will
  get slightly more cumbersome later.
* Other minor code movement to reduce later diffs.

Bug: none
Change-Id: I87d466901608191d9be3ecd0cbeea256e68e2937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021462
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737911}

https://chromium.googlesource.com/openscreen.git/+log/1ccc65258d95..76cf904a4fd4

git log 1ccc65258d95..76cf904a4fd4 --date=short --first-parent --format='%ad %ae %s'
2020-02-03 jophba@chromium.org Improve raspberry pi documentation
2020-02-03 jophba@chromium.org Issue 98: Offer message for aac codec

Created with:
  gclient setdep -r src/third_party/openscreen/src@76cf904a4fd4

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/openscreen-chromium
Please CC jophba@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

Bug: None
Tbr: jophba@chromium.org
Change-Id: I4745775e39e9d9f22e6fcfef597f9c9055785640
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036335Reviewed-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@{#737910}

Revert "[Controls Refresh] Regression: Focus is not seen on color selector icon when the focus is traversed using Tab key."

This reverts commit 2292ef33.

Reason for revert: Change got in while missing a few WPT baselines for mac builds

Original change's description:
> [Controls Refresh] Regression: Focus is not seen on color selector icon when the focus is traversed using Tab key.
> 
> This change addresses the bug in which the color picker selection
> ring gets placed in the top left corner after closing a color picker
> with (255,255,255) is selected.
> 
> Bug: 1046648
> Change-Id: Idb82a962c0ba40338c4a38c5c5526dea7339c5a8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032420
> Reviewed-by: Kent Tamura <tkent@chromium.org>
> Reviewed-by: Mason Freed <masonfreed@chromium.org>
> Reviewed-by: Sanket Joshi <sajos@microsoft.com>
> Commit-Queue: Sam Sebree <sasebree@microsoft.com>
> Cr-Commit-Position: refs/heads/master@{#737900}

TBR=tkent@chromium.org,masonfreed@chromium.org,sajos@microsoft.com,sasebree@microsoft.com

Change-Id: Ida95ca36bc3cd1b68af1518c1cfd6d41d76a75e2
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1046648
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036437Reviewed-by: Sanket Joshi <sajos@microsoft.com>
Commit-Queue: Sam Sebree <sasebree@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#737909}

BUG=1023913

Change-Id: Ib92e5904843229f4e4d1d1fb2cdfa12cfb8db54f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032077
Auto-Submit: Avi Drissman <avi@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737908}

The information is extracted from the shortcuts.xml resource if present
in the WebAPK.

This is needed to diff with a new WebApkInfo generated from the web app
manifest for update decisions.

Bug: 1045588
Change-Id: Ibe5284d22799e5d5d5c37e53da3da95c6903a5ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027417
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737907}

Records the image bytes, subframe image bytes, media bytes as UKM from
the PLM infra.

UKM privacy review doc:
https://docs.google.com/document/d/133SsQTd3L5ryQaI-q1rZsh6EeTsE_HxDFlthjlXi4CU/

Bug: 1047325
Change-Id: Ib77da45c07a2f55bea77a9750b4c69c7584ecf5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032002Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: rajendrant <rajendrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737906}

The change makes all proto fields optional, and slightly simplifies the
decoding logic.

CookieChangeSubscription::Serialize() sets all the proto's fields, so
the change is only relevant for corrupt protos. In this case, proto3
will report default values for missing fields.

The change is compatible with previously written data, as proto2 and
proto3 use the same on-disk format.

Bug: 729800
Change-Id: I06b08ce003b571b716bccd540fa15918ea925bb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036393Reviewed-by: Ayu Ishii <ayui@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737905}

BUG=1023913

Change-Id: Ibd15e2c76413639c0caf8d1d255add07a815bcdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033986
Auto-Submit: Avi Drissman <avi@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737904}

This is a reland of 71d64a4f

Original change's description:
> [IndexedDB] Remove child policy permissions for blobs from IndexedDB
> 
> Now that blobs from IndexedDB are backed & read by the IndexedDB system,
> they are no longer sent to the renderer as files. This means no content
> policy changes or grants are necessary.
> 
> Tracking document:
> https://docs.google.com/document/d/18suNOOzuEJbqgRJF0MB2VqdTyYqS4cvI2PGaCpyPXSw/edit?ts=5de6dc30&pli=1#heading=h.tw2iw2qfgduj
> 
> Bug: 1015212
> Change-Id: If3d2fd80b3254f19a56ab16ed7fc39cf5f0cf684
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1955813
> Reviewed-by: Ken Rockot <rockot@google.com>
> Reviewed-by: enne <enne@chromium.org>
> Commit-Queue: Daniel Murphy <dmurph@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#722617}

Bug: 1015212
Change-Id: I4edcd6b1c79005c78c5ecf859cb6807559013a86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036431Reviewed-by: enne <enne@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737903}

This CL cleans up the experiments to give all the builders a clean
start before enabling the feature on by default, and the reason is that
it will be easier to compare the cycle time before and after to measure
the impact.

Bug: 838735
Change-Id: I7809eafa0d3294d90087e8dde4928a5e88704a64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036512Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737902}

This has been accidentally removed in
https://chromium-review.googlesource.com/c/chromium/src/+/1994427/10/chrome/browser/ui/webui/discards/discards_ui.cc#b215

Change-Id: Id5de050d8c1fa84ce0137abd87c1650b35aef084
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036190Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Auto-Submit: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737901}

[Controls Refresh] Regression: Focus is not seen on color selector icon when the focus is traversed using Tab key.

This change addresses the bug in which the color picker selection
ring gets placed in the top left corner after closing a color picker
with (255,255,255) is selected.

Bug: 1046648
Change-Id: Idb82a962c0ba40338c4a38c5c5526dea7339c5a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032420Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Sanket Joshi <sajos@microsoft.com>
Commit-Queue: Sam Sebree <sasebree@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#737900}

To show the app list a user can scroll up from the shelf with the
touchpad or the mouse. This gesture needs to ignore the australian and
the reverse scroll to feel more natural for the user.

Bug: 1035918
Change-Id: I3de6cac2b84bbfbba5a0f678a529222797078ac6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004952Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Ana Salazar <anasalazar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737899}

Bug: 1026426
Change-Id: I28820e7694879716d8883f7ba2d2a4c9780b48f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032090
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737898}

Using this flag is not supported on particular chipsets.

R=liberato@chromium.org,vikassoni@chromium.org

Bug: 1021007
Change-Id: I8b4e29e2789884463b555cb989f5c7278b7fce50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036374
Commit-Queue: Khushal <khushalsagar@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Auto-Submit: Khushal <khushalsagar@chromium.org>
Reviewed-by: vikas soni <vikassoni@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737897}

Chromium compiles with the 10.14 SDK, so remove old code that handled
the case where it compiled with previous SDKs.

Also update property accesses to use property syntax.

Bug: 1044838
Change-Id: Ib7f2e5cd2cfc436dd815e5861d0448262f43955c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021024
Auto-Submit: Avi Drissman <avi@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737896}

The crash is because DirectRenderer schedules a primary plane as
overlay, however the previous submitted frame has been released due to
reshaping. To fix it, we need to make sure to redraw the whole frame if
reshape is requested.

Bug: 1044678,1048149
Change-Id: Id978fbce86a6481e976828ccea51abf883ac642f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030627
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737895}

https://skia.googlesource.com/skia.git/+log/5ddc34ca3de6..23e2ad174cfa

git log 5ddc34ca3de6..23e2ad174cfa --date=short --first-parent --format='%ad %ae %s'
2020-02-03 sgilhuly@chromium.org SkiaDawn: Connect GrIOType in onWrapBackendTexture
2020-02-03 scroggo@google.com Allow decoding without color conversion
2020-02-03 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2020-02-03 robertphillips@google.com Make exoticformats GM a bit easier to triage

Created with:
  gclient setdep -r src/third_party/skia@23e2ad174cfa

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC scroggo@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: scroggo@google.com
Change-Id: Idf85ec6c79d051ce29d04687f63cd28e3a566473
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036332Reviewed-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@{#737894}

Bug: 1011049
Change-Id: I99996411a41f0383dd252b758663bb0f6b12276d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032793
Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#737893}