GitLab

This patch changes |NGInlineCursor::PositionForPointInInlineBox()| to call
|NGInlineCursor::PositionForPoint()| for |closest_child_after| like it does
fro |closest_child_before| to make hit test on left edge of RTL inline element
to pass the test[1].

This patch also changes |NGFragmentItem::PositionForPointInText()| to avoid
calculating position for items of |IsGeneratedText()|, e.g. ::before/::after.

This is follow-up of the CL[2] which introduces calling |PositionForPoint()|
for |closest_child_before|.

[1] editing/selection/caret-at-bidi-boundary.html
[2] http://crrev.com/c/2104812 [NGFragmentItem] Fix hit test on
position:relative inline element

Bug: 707656
Change-Id: I8aca51af66a7d1885b7b7c2627cd7f4131b37c47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2282721
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786076}

To convert from screen coordinates to the normalized absolute
coordinates dimensions used by SendInput, the scaling factor should be
(65536.0 / screen_dimension).

Previously, we used (65535.0 / (screen_dimension - 1)). Although the
difference between these two factors is small, the discrepancy becomes
more prominent when it's multiplied out. This discrepancy may lead to
the computed absolute coordinates being off by a pixel or two depending
on the resolution of the screen in question.

Change-Id: Id305abc6ddf904ffbbb07dc740c655ac1be3cf83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2278347Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Chege Gitau <dagitau@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#786075}

This will be used in Kaleidoscope to match against providers returned
from the API. Providers with matching origins will be considered
high watch time, and we will suggest them to the user.

Change-Id: Ic1181dde499ad39094442bd555a1b3b541f5ca2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277091Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Sam Bowen <sgbowen@google.com>
Cr-Commit-Position: refs/heads/master@{#786074}

Bug: None
Test: Build
Change-Id: I98fdd4ac735dd1cf4e107cc6bb85570ae2114ae1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284845Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Auto-Submit: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786073}

Bug: 1098328
Change-Id: I56d1d821da8824258d4b84ef6e50ef805402a622
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274777
Commit-Queue: Maxime Charland <mcharland@google.com>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786072}

Design doc: go/appservice-adaptive-icon

The related ARC icon interfaces are modified/added to use the new
structure RawIconPngData, and call AppService interfaces to
decode/encode the icon.

The ARC side CL number is 12024464, which has use the new
OnTaskDescriptionUpdated interface. And we can't call both the new and
old task update interfaces, that could cause updating twice for the icon
on the windows, so we have to select 1(the new one) to use in the code.

Once the ARC side CL is submitted, the change on the Chromium side will
be change to use the new interface as soon as possible.

TODO: Add some test cases for adaptive icons and implement the new
interfaces for FakeAppInstance.

Note: Below 2 files will be deleted soon. They are modified to pass the
build:
chrome/browser/ui/ash/launcher/arc_app_window_launcher_controller.h
chrome/browser/ui/ash/launcher/arc_app_window_launcher_controller.cc

BUG=1083331

Change-Id: I8daaa1643dd20c6038d685863c8f6e71c3948c7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2251600Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Long Cheng <lgcheng@google.com>
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786071}

https://skia.googlesource.com/skia.git/+log/b4d60f807dbd..bb61fe324575

2020-07-07 jvanverth@google.com Hoist up submit for resolves
2020-07-07 brianosman@google.com Always use Skia's Vulkan headers when compiling particles module
2020-07-07 jvanverth@google.com Add D3D support for MSAA
2020-07-07 brianosman@google.com Remove GrCoordTransform entirely
2020-07-07 johnstiles@google.com Add support for an inputFP in SkMixerColorFilter::asFragmentProcessor.
2020-07-07 herb@google.com use SkTInternalLList in SubRun
2020-07-07 johnstiles@google.com Update GrConfigConversionEffect to use an input FP.
2020-07-07 herb@google.com consolidate text op creation

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 mtklein@google.com on the revert to ensure that a human
is aware of the problem.

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

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

Cq-Include-Trybots: luci.chromium.try: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: mtklein@google.com
Change-Id: I965c7f981b5233a59460d54d3c206a1d372b5320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285217Reviewed-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@{#786070}

Bug: 1093374
Change-Id: Ifbce5ef6720b7bc449167ab2a3b5471d20625596
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283925Reviewed-by: Travis Skare <skare@chromium.org>
Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786069}

The 1-parameter version is simpler, and the 2-parameter version is
deprecated.

Bug: 1009837
Change-Id: I083906f5cb2f899814511707a639da591a711182
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285177Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786068}

https://chromium.googlesource.com/webm/libvpx.git/+log/de4aedaec33c..a1cee8dc919d

$ git log de4aedaec..a1cee8dc9 --date=short --no-merges --format='%ad %ae %s'
2020-07-06 marpan vp9: Update last_q for dropped frames
2020-07-06 marpan vp9: Fix to use last_q for resize check
2020-06-30 bsreerenj vp9-svc: Fix the bitrate control for spatial svc
2020-06-29 jzern add CONTRIBUTING.md
2020-06-24 jinbo-hf vp8,vpx_dsp:[loongson] fix specification of instruction name

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=jzern@google.com

Change-Id: I878d5932fb02f144392739671ac67750eddb8755
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285163Reviewed-by: James Zern <jzern@google.com>
Commit-Queue: Marco Paniconi <marpan@google.com>
Cr-Commit-Position: refs/heads/master@{#786067}

The goal is to remove GetSkImage() from PaintImage since when texture
backed, this API may incur the cost of a GPU to CPU readback. By using
GetSkImageInfo() for image metadata, we can avoid expensive calls to
GetSkImage(). This change replaces some of the remaining callers of
GetSkImage().

More details about overall PaintImage effort: crbug.com/1023259
Info about the OOPR-Canvas2D project: crbug.com/1018894

Bug: 1031050
Change-Id: Id7b3d8e779784d9790a43b922f4470234b17795d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2242653
Commit-Queue: Jonah Chin <jochin@microsoft.com>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786066}

This patch fixes legacy list markers so that they are autosized even if
their 'content' property is set to something different than 'normal'.

Bug: 457718

TEST=fast/text-autosizing/list-marker-numbered-with-content-and-autosizing.html

Change-Id: I32360a2868b41cfd4d055b3b7efcd73fb9b5adee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2258732
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786065}

This change fixes the issue on touch devices where the narrator sets
focus into an editable element and expect the VK to come up on double
tap. Here the touch/gesture events are handled by the narrator and thus
the events are not delivered to Chromium. This results in a pointer
type as "unknown" in |RenderWidgetHostViewAura| so it fails the check
where we decide to call the system API to display the VK.
Here if we are getting a text input state update which is of type
something other than none, there is a focused accessibility node, and
|show_ime_if_needed| flag is set, then we can call the system API to
show the VK.

Bug: 1100390

Change-Id: I4c13474b4b4655f506429a724b3648efb81fec74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274865Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Commit-Queue: Anupam Snigdha <snianu@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#786064}

Since fixed and sticky positioned elements are always composited,
this will be correct. This removes one dependency on compositing state.

Bug: 1100711

Change-Id: I310b25cff1dd7ead16e6fa4b95e12ed7a3de255b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2280588
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786063}

Add a check to make sure the content directory handle list size doesn't
exceed the 16 bit handle-id space.

Test: web_engine_unittests
Bug: 1073176
Change-Id: I0a90f5bcca35a3c0e29e605bda9c6439092d3d29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283556
Commit-Queue: Sharon Yang <yangsharon@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786062}

This CL adds a wrapper of DownloadLaterDialogCoordinator, and use it
to implement the change button flow in download home.

Bug: 1102230,1078454
Change-Id: I16d3499ad3b491b50fbde2e0f88dfe80a3623fe5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2281091
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: Hesen Zhang <hesen@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786061}

This also ended up touching some of //device/bluetooth.

Bug: 834319, 1007786
Change-Id: Iebcf042a74af77d3aac2cce8afb4fc4d2af9d831
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285450
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786060}

https://github.com/WICG/native-file-system/issues/194 suggests there
might be something weird going here, so add assertions to the tests to
make sure locked has the value we expect it to have.

Change-Id: Ia13251aeeb16734047a2f5abe7e61d7fd4bbeb0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285293
Auto-Submit: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786059}

For simple boolean equality checks, this converts those to
the Callable<Boolean> syntax, for all other checks, these are
converted to Criteria.checkThat(...);

BUG=1071247

Change-Id: I87aa7296e3c71d7ad0c7eb26c20109a1e788e91e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285255Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786058}

Changes to other AndroidX libraries where generated automatically by the
fetch_all.py script.

Bug: 1102962
Change-Id: I1cbb8b28d24d64ff4620659987b6e92a6a66af19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283413Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Commit-Queue: Yaron Friedman <yfriedman@chromium.org>
Auto-Submit: Carlos Knippschild <carlosk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786057}

in /chrome/android/feed

This CL was uploaded by git cl split.

R=harringtond@chromium.org

Bug: 1071603
Change-Id: I0297bc1e20b546cf42085c766c00e8448c2a6b76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285492
Auto-Submit: Evan Stade <estade@chromium.org>
Reviewed-by: Dan H <harringtond@chromium.org>
Commit-Queue: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786056}

On partner foldable phones, when the secondary display is off, there
is only one targetable displays and only #onDisplayChanged is called.
This CL tries to merge tabs #onDisplayChanged as well.

Bug: 1088202
Change-Id: Id21960b40bceb4b04fce7a2718c0e33bee0f4920
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2272131Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Lijin Shen <lazzzis@google.com>
Cr-Commit-Position: refs/heads/master@{#786055}

This is pushed back to the same date as the other copy/copy histograms
in
https://chromium-review.googlesource.com/c/chromium/src/+/2276218

Bug: 1102476
Change-Id: I4dfb295ca08eb1c3310c12e2ff56a6623b01b3c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285175
Auto-Submit: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786054}

The clean-up is based on the comments left by japhet@ on

https://chromium-review.googlesource.com/c/chromium/src/+/2276401

Bug: None
Change-Id: Ifa6744a4299383bad5089589a93b1c99cb40ddc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284400Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Dylan Cutler <dylancutler@google.com>
Cr-Commit-Position: refs/heads/master@{#786053}

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

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

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

Tbr: perfetto-bugs@google.com
Change-Id: Ib89714aa5abcbb587665efad0b9c1988c76b4402
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285384Reviewed-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@{#786052}

Change-Id: Ie758db5d7cd3d29c51be8b15ef8c724243d9eaa7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276495
Commit-Queue: Jarryd Goodman <jarrydg@chromium.org>
Auto-Submit: Jarryd Goodman <jarrydg@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786051}

Flaky tests include: (FileDisplay|QuickView)/FilesAppBrowserTest.Test/(fileDisplayDrive|openQuickView|fileDisplayDownloads)_TabletMode.

Flake occurrences can be viewed at https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyOgsSBUZsYWtlIi9jaHJvbWl1bUBicm93c2VyX3Rlc3RzQEZpbGVzQXBwQnJvd3NlclRlc3QuVGVzdAw

TBR: lucmult@chromium.org
Bug: 1102947
Change-Id: Id39ff39a94e955f0a513b7e5ddceef264846beae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285298Reviewed-by: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786050}

I included overloads for setting the source scheme with either a boolean
or the scheme string itself.

I refacted other similar utility functions in cookie_util.cc to reuse
this new function as well.

Bug: 1102874
Change-Id: I879ea6534f65ab54d4374fb768a751115e68471b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285244Reviewed-by: Lily Chen <chlily@chromium.org>
Commit-Queue: Dylan Cutler <dylancutler@google.com>
Cr-Commit-Position: refs/heads/master@{#786049}

There is a check for the background color painting border
being renderable (for rounded corners) but the check is
overlooked for the image rect. Fix that by treating the
image fill rect the same way we treat the color rect.

Bug: 1101080
Change-Id: I4328357f41793d00002cb80d27bd7182d1756be7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283775
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#786048}

Tricium flagged this constructor in crrev.com/c/2261190 since single-
argument constructors can result in unintentional implicit conversions.
Mark the constructor as explicit and update the remaining call sites to
match.

Bug: 1098859
Change-Id: Ied51476ad87473a4ceb2349cc7b1a71b0eabf60e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274860
Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786047}

Previously, the call to WebPlatformMediaStreamSource::SetOwner() was
encapsulated by WebMediaStreamSource::SetPlatformSource().

Now that we have moved away from operating over WebMediaStreamSource
directly in Blink, it is needed that callers do something like

  WebPlatformMediaStreamSource::SetOwner(MediaStreamSource)
  MediaStreamSource::SetPlatformSource(WebPlatformMediaStreamSource)

... manually.

This CL simplifies the call sites by moving
WebPlatformMediaStreamSource::SetOwner() within
MediaStreamSource::SetPlatformSource(), and updating the current callsites.

BUG=704136
R=guidou@chromium.org
TBR=guidou@chromium.org

Change-Id: Iff1d35b56086650c0012cc0fbc3baf088be67e6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283579
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786046}

This adds a new strings file for Nearby UI. Also adds strings and an
icon used in the notifications for Nearby.

Bug: 1102348
Change-Id: Ic5efac87078ad5bd9e26b714952395fcaabad995
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283306Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Commit-Queue: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786045}

Previously, the caption button container would always paint in active or
inactive frame colors as appropriate. However, for themes with a
different frame/caption and tab background color, in normal tabbed
browser mode, this would result in the buttons painting against the
wrong background color.

Now whether or not the container paints its background can be controlled
by external code.

Bug: 1099195
Change-Id: I6c46de4f9eb423a0aecb9ccee03231ca42dfb462
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284447Reviewed-by: Caroline Rising <corising@chromium.org>
Commit-Queue: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786044}

When titles-UI is disabled, the omnibox additional text will only
contain URLs and never page titles. We can safely style it blue in this
case.

When title-UI is enabled, it can contain either URLs or page titles.
Ideally, it would be styled blue/black appropriately dynamically, but
given it seems title-UI won't launch, we don't have to worry about this
case for now.

Change-Id: Id4bf756e23d5c0678665343c3cbe4c6e14fb8780
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283949
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786043}

Bug: 1098899
Change-Id: Iae357fc998a662ed23bf1496a4ec21a12593f2cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285331
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786042}

Hard-coded language indexes need to be updated since the list of
supported languages changed in iOS 14.

BUG=1102968

Change-Id: I8ec7961dfcf2437840406894e47fc87444d7a5cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285338
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786041}

Disable on Mac arm for now to allow Chrome to compile on that arch.

This should be replaced by an actual implementation to provide
performance profiles for the architecture in the UMA Sampling
Profiler dashboard and support stack capture during slow reports
tracing to diagnose pathological performance problems in the wild.

Bug: 1102197
Change-Id: Ie45272f30b75f14706490cef9eeb6402e3a70c0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284618
Commit-Queue: Mike Wittman <wittman@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Mike Wittman <wittman@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786040}

The 1-parameter version is simpler, and the 2-parameter version is
deprecated.

Bug: 1009837
Change-Id: I74f7c0697d077d5cdea3501a86a558911762e3ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284366Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786039}

The term 'End of life' gives the impression that the device would no
longer be usable. But in the context of minimum chrome version, it means
no future updates are possible.
As Auto Update Expiration is a preferred term over End of Life, this CL
migrates any user facing data for the minimum chrome version policies
from eol/End of Life to aue/Auto Update Expiration.
We continue to use eol/End Of Life in the code.

Bug: 1048607
Change-Id: I82d38ea562cfe30be05fc7ddc32ae3e8ec9e50d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2279762
Commit-Queue: Saurabh Nijhara <snijhara@google.com>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#786038}

https://chromium.googlesource.com/angle/angle.git/+log/6fc53fdb8bb1..3688cb363ccd

2020-07-07 nguyenmh@google.com Fix bugs in angle_end2end_tests and frame capture
2020-07-07 jiajie.hu@intel.com Remove a few hardcoded path to libjpeg_turbo
2020-07-07 etienneb@chromium.org Enable the use of chromium worker pool

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

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

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

Cq-Include-Trybots: luci.chromium.try: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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: chromium:1091259
Tbr: syoussefi@google.com
Change-Id: I9745c96236a15243ee9ec47e1925cf40fb9e2f11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2285212Reviewed-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@{#786037}