GitLab

This reverts commit 786fad53.

Reason for revert: might have caused failures in layout tests. https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Mac10.13%20(retina)/14152

Original change's description:
> Revert "Skip MISSED frames in browser compositor"
> 
> This reverts commit 1374013c.
> 
> Reason for revert: causes jank https://crbug.com/947587
> The original reason for landing this CL does not apply anymore. It is
> no longer the case that viz skips a BeginFrame if an undrawn frame
> exists. See https://crrev.com/c/1521967
> 
> Original change's description:
> > Skip MISSED frames in browser compositor
> > 
> > This CL fixes a dropped frame issue when a scroll transitions from
> > dragging to a momentum "fling" phase. When the user is scrolling and
> > lifts their finger with velocity, the scroll continues according to a
> > decelerating animation curve. When this happens, the FlingController
> > receives a FlingStart instead of a ScrollUpdate and it uses that to
> > create an animation curve.
> > 
> > When this happens the browser process registers itself as an animation
> > observer so that it begins to receive BeginFrame signals. However, the
> > display service issues a MISSED BeginFrame for the frame in which the
> > animation was registered. This will frequently miss submission in the
> > current frame, so it submit next frame and won't receive a BeginFrame
> > then. This leads to a frame without the browser ticking the fling
> > animation. See https://crbug.com/882907#c50 for a diagram and more
> > complete explanation of the issue.
> > 
> > The browser process shouldn't require processing MISSED frames so in
> > this CL we simply drop MISSED frames if we're in the browser compositor
> > (commit_to_active_tree is true). Longer term, the display scheduler
> > should make these decisions but this is an immediate fix for the fling
> > issue.
> > 
> > Bug: 882907
> > Change-Id: Ieb6d14051dc05c5e177da1920dbd27684f941d29
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1517164
> > Commit-Queue: David Bokan <bokan@chromium.org>
> > Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#640172}
> 
> TBR=bokan@chromium.org,sunnyps@chromium.org
> 
> # Not skipping CQ checks because original CL landed > 1 day ago.
> 
> Bug: 947587,882907
> Change-Id: I216a0aa63a39f5046879e49209702c1bc318bbd6
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610853
> Reviewed-by: Saman Sami <samans@chromium.org>
> Reviewed-by: David Bokan <bokan@chromium.org>
> Commit-Queue: Saman Sami <samans@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#659479}

TBR=bokan@chromium.org,sunnyps@chromium.org,samans@chromium.org

Change-Id: I4324ee568a61831a3bfae898c7c2141da009c385
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 947587, 882907
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611508Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659499}

This reverts commit f19a4c81.

Reason for revert:

Breaks https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-dbg

Sample failure line:
[ RUN      ] AppMenuModelTest.Basics
[31511:31511:0513/150125.044037:3461088700:FATAL:window.cc(91)] Check failed: env || !g_env_arg_required_string. Within ash you must supply a non-null aura::Env when creating a Window, use window_factory, or supply the Env obtained from Shell::Get()->aura_env()

Causes ~1000 tests to fail.

Original change's description:
> views: random cleanup from removing support for mus
> 
> This functionality was added purely for mus and is no longer necessary.
> 
> BUG=958241
> TEST=purely dead code removal
> 
> Change-Id: I856576f9adef9728d837d56e82f94a87aeea040b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610497
> Commit-Queue: Scott Violet <sky@chromium.org>
> Reviewed-by: Evan Stade <estade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#659207}

TBR=sky@chromium.org,estade@chromium.org

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

These should synchronously work, so allow them in extension Service
Worker contexts.

Also add tests for these.

Bug: None
Change-Id: I2d1f181bbbe8991546bc79e48ca51ed181d6a260
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610855Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659497}

Properly initialize ActionInfo::default_state to the appropriate value
based on the type of action (default enabled for browser actions and
the generic "action" key, default disabled for page actions). Use this
value (instead of inferring from the action type) on ExtensionAction
to initialize the enabled/visible state.

Also move the restriction for default_state from ExtensionActionHandler
to ActionInfo, where the rest of the action validation is.

Finally, add unittests for the parsing of the default_state key in the
manifest, and move the existing tests that verify it isn't allowed for
page/browser actions to the extension_action_handler_unittest.cc file.

Bug: 893373

Change-Id: I14c2f8f92b7cac52fa3e6bcbb10420480a853486
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584718
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659496}

Bug: 956495
Change-Id: If86a4618eb2865e3bf63a6bfdc3d92096d7f747b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591839Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659495}

Previous to this CL, overlap checking was incorrect for layers
that had a pixel-moving backdrop-filter applied. The WPT test
external/wpt/css/filter-effects/backdrop-filter-paint-order.html
was the best indicator of this bug - a backdrop-filter painted
*after* adjoining but not overlapping content would be improperly
merged, and blurred content would be observed. This is now fixed.

Bug: 622128
Change-Id: I07539f5fbdc9c6e9cfaf6d4116b8de3dd62d1e94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607101
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659494}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/94454d8433df..69d66c506c56


Created with:
  gclient setdep -r src-internal@69d66c506c56

The AutoRoll server is located here: https://autoroll-internal.skia.org/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=fergal@google.com,avi@google.com,btolsch@google.com,andypaicu@google.com

Change-Id: I1c5378a8db60fe3cf4cdcaf3146515d7266294d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610201Reviewed-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@{#659493}

These were mistakenly not marked as obsolete when crrev.com/c/1574281
landed.

Bug: 829042
Change-Id: I1061f521b00f9a3c936902153fdd1432dcdac198
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611282Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659492}

It is preferred to use the method IsUnifiedConsentFeatureEnabled()
instead of using the kUnifiedConsentFeature feature directly. This CL
replaces all explicit usages kUnifiedConsentFeature with
IsUnifiedConsentFeatureEnabled.

Bug: None
Change-Id: I09a18a7592466774d703baab6e0dd50f08ddace0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599016
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659491}

Non-behavior changing refactoring.

Split visitors into:
- MarkingVisitorBase and MarkingVisitor
- UnifiedHeapMarkingVisitorBase and UnifiedHeapMarkingVisitor

The *Base classes are supposed to be used in concurrent settings while
the ones without suffix are main-thread only. The main-thread versions
also provide write barriers.

Bug: 945806
Change-Id: I01f45b381b328b6b10c62394444c9e7a989b6085
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609916
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659490}

This will be used to assess compatibility risk for Payment Request API
changes.

Bug: 821771
Change-Id: I727c0b986c24bd8c741907abdbaa8cd1b4e3c276
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607406Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Danyao Wang <danyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659489}

Changes the font of the text fields to a preffered font in order to
support dynamic type fonts.

Bug: 959764, 951300
Change-Id: I785a5c577d69e33018a7de5403a0e96751b3d455
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611601
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Auto-Submit: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659488}

This makes Voice Over not read the siblings views of the alert when
presented. That is the content behind the chrome and the alert.
Everything outside or above the alert view will be read.

Bug: 959764, 951300
Change-Id: Idb932e1fcc251899bccbb7b834e022432c740973
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611607
Auto-Submit: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659487}

With BlinkGenPropertyTrees shipping, we can update the paint
documentation to remove references to the old system (SPV175).
This patch has the following changes:
*) Improved overview section (about 1/3 from the top)
*) Removed the SlimmingPaintV175 section
*) Removed references to BlinkGenPropertyTrees
*) Swapped the order of "Paint invalidation" and "Building paint property trees"
*) A short description of how paint works (there was none before)
*) Typeo fixes

Change-Id: I7a45bb7daefd44642cc000e268e0808faf80e633
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604462
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659486}

This reverts commit 4c019ae1.

Reason for revert: Broken compile step on Windows debug GPU bot, see https://crbug.com/962942.

Original change's description:
> Roll src/third_party/pdfium 726ece1b5340..2169a778183b (1 commits)
> 
> https://pdfium.googlesource.com/pdfium.git/+log/726ece1b5340..2169a778183b
> 
> 
> git log 726ece1b5340..2169a778183b --date=short --no-merges --format='%ad %ae %s'
> 2019-05-14 thomasanderson@chromium.org Move pdfium sources into fpdfsdk
> 
> 
> Created with:
>   gclient setdep -r src/third_party/pdfium@2169a778183b
> 
> 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.
> 
> 
> 
> BUG=chromium:960288
> TBR=pdfium-deps-rolls@chromium.org
> 
> Change-Id: I41be15646bb372865d104d30144a6f90eec5ae61
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610890
> Reviewed-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@{#659360}

TBR=chromium-autoroll@skia-public.iam.gserviceaccount.com,pdfium-deps-rolls@chromium.org

Change-Id: I1c404aca96ac1028cd48b5d8d042fc26d68443f5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:960288, chromium:962942
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611743Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659485}

Bug: 962677,960322
Change-Id: I6c33767531b7416469cb1766b41299d15398885b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610764
Auto-Submit: Christos Froussios <cfroussios@chromium.org>
Commit-Queue: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659484}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ca6dbeca..9cbdd437

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

SyncSettingsTableViewController is only used pre-Unified Consent and
DCHECKs that Unified Consent is disabled. This CL ensures that
SyncSettingsTableViewControllerTest runs with Unified Consent disable.

This is a pre-requisite for enabling Unified Consent by default on iOS.

Bug: 960260
Change-Id: I0499985052763eeac1fb640701b341ccdcdfc949
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611605Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659482}

https://skia.googlesource.com/skia.git/+log/136ad09848f5..c2aea5938d0d


git log 136ad09848f5..c2aea5938d0d --date=short --no-merges --format='%ad %ae %s'
2019-05-14 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (nontrivial).


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

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

Change-Id: Ie277cbba56e98c7ae0f920d1915b6ad87560895f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611759Reviewed-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@{#659481}

Adding comments for ChromeIdentityService to accept nil as |callback| for
ChromeIdentityService::GetAvatarForIdentity().
And Adding support for nil callback in FakeChromeIdentityService.

Related to: crrev.com/i/1296954

Change-Id: I0d96d8a3abcd934705ec7743d7711b760ea1b459
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609842
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659480}

This reverts commit 1374013c.

Reason for revert: causes jank https://crbug.com/947587
The original reason for landing this CL does not apply anymore. It is
no longer the case that viz skips a BeginFrame if an undrawn frame
exists. See https://crrev.com/c/1521967

Original change's description:
> Skip MISSED frames in browser compositor
> 
> This CL fixes a dropped frame issue when a scroll transitions from
> dragging to a momentum "fling" phase. When the user is scrolling and
> lifts their finger with velocity, the scroll continues according to a
> decelerating animation curve. When this happens, the FlingController
> receives a FlingStart instead of a ScrollUpdate and it uses that to
> create an animation curve.
> 
> When this happens the browser process registers itself as an animation
> observer so that it begins to receive BeginFrame signals. However, the
> display service issues a MISSED BeginFrame for the frame in which the
> animation was registered. This will frequently miss submission in the
> current frame, so it submit next frame and won't receive a BeginFrame
> then. This leads to a frame without the browser ticking the fling
> animation. See https://crbug.com/882907#c50 for a diagram and more
> complete explanation of the issue.
> 
> The browser process shouldn't require processing MISSED frames so in
> this CL we simply drop MISSED frames if we're in the browser compositor
> (commit_to_active_tree is true). Longer term, the display scheduler
> should make these decisions but this is an immediate fix for the fling
> issue.
> 
> Bug: 882907
> Change-Id: Ieb6d14051dc05c5e177da1920dbd27684f941d29
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1517164
> Commit-Queue: David Bokan <bokan@chromium.org>
> Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#640172}

TBR=bokan@chromium.org,sunnyps@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 947587,882907
Change-Id: I216a0aa63a39f5046879e49209702c1bc318bbd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610853Reviewed-by: Saman Sami <samans@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659479}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/394095a0eb17..94454d8433df


Created with:
  gclient setdep -r src-internal@94454d8433df

The AutoRoll server is located here: https://autoroll-internal.skia.org/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=fergal@google.com,avi@google.com,btolsch@google.com,andypaicu@google.com

Change-Id: I4705c623f188abde12b2121c9e7b920c37543dcd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611761Reviewed-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@{#659478}

Since the platform-independent code doesn't support scrolling a node to
a particular location in the window, we calculate the appropriate offset
for each type of scroll and scroll using the ScrollTo API.

Bug: 932708
Change-Id: I2428a40815e276ffe51620496d7782b6340347ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602713Reviewed-by: Joanmarie Diggs <jdiggs@igalia.com>
Commit-Queue: Martin Robinson <mrobinson@igalia.com>
Cr-Commit-Position: refs/heads/master@{#659477}

Proguard mapping files are necessary for java_deobfuscate to be useful,
so make sure to list them as data dependencies.

Bug: 962540
Change-Id: Iecf24da4904943f4307679c993b213f1e556d823
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609846
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659476}

Bug: 962126

We typically lock this mutex before reading or writing to
decode_failed_. Do so in one more place to avoid a data race.

Change-Id: I0248e4dd99defc5ad3d09575096847e6455adfc9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610085Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Auto-Submit: Leon Scroggins <scroggo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659475}

The render_view_termination_status_ is assigned, but never referenced.
This CL removes it, as it is unused code.

Bug: 566116
Change-Id: I40363c1fa9bf028c2fcd44e5e37e26efd4ec1a03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611245Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659474}

Or mark them as platform-specific.

Change-Id: I9f02c101b3df5306ea8d18fc3b3041573510c86c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1420275
Commit-Queue: sebsg <sebsg@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659473}

Bug: 962290
Change-Id: Ia7e3ee0e72fc3acecf8246fc2c28ef3ca604e206
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609829
Commit-Queue: Anastasiia Nikolaienko <anastasiian@google.com>
Reviewed-by: Kush Sinha <sinhak@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659472}

This is no-op: we don't have any chrome UI on Fuchsia, but we will
want to use OOP when any UI is added.

Bug: 962617
Change-Id: I9aea13556e2c49101f15d1935f465de353964c9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611220Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659471}

Follow-up to
https://chromium-review.googlesource.com/c/chromium/src/+/1606402 which
moves CreateContentMainDelegate() under a !OS_ANDROID #ifdef.

Bug: 961849
Test: Compiled chromecast/app:test_support on Android.
Change-Id: I3b9cf531728407be1280d767f8573e2d9cf72c5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610751
Auto-Submit: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659470}

Add more text to components/services/README about some more reasons why a service is there instead of /services.

Change-Id: I93b26022d0391ef3daa18d9b21ee55777eebfe34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610537Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Auto-Submit: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659469}

Adds benchmarks to test JPEG decoding performance for images with the
following chroma sampling ratios: h1v1, h2v1, h1v2 and h2v2.

Most images on the Web use sampling ratios h2v2, h2v1 or no sampling
at all (h1v1). We also add a test for h1v2 sampling as this is used
when an h2v1-sampled image is rotated by 90 or 270 degrees.

Adding these additional benchmarks is a precursor to adding Arm NEON
performance optimizations to JPEG decoding.

Bug: 922430
Change-Id: I6bdc9516658f2b884c09a03bfc01bd2e1c091c34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599570Reviewed-by: Chris Blume <cblume@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Jonathan Wright <jonathan.wright@arm.com>
Cr-Commit-Position: refs/heads/master@{#659468}

Bug: 962871
Change-Id: I8070e3bf7b210f39b905ce4e335cd1e7e44e4c55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610770Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659467}

This CL ensures that all tests in theSigninIntegrationTest pass
when the Unified Consent Feature is enabled. In achieves this in
the following steps.

1. It splits the SigninInteractionControllerTestCase class in 3:
a) SigninInteractionControllerTestCase: test cases that pass both when
Unified consent is enabled or disabled;
b) SigninInteractionControllerUnityDisabledTestCase: test cases that require
Unified Consent to be disabled;
c) SigninInteractionControllerUnityEnabledTestCase: test cases that require
Unified Consent to be enabled;

2. It updates all necessary tests in the SigninInteractionControllerTestCase
to pass when the Unified Consent is enabled.

3. It includes SigninInteractionControllerTestCase both in
ios_chrome_ui_egtests (that run with Unified Consent enabled) and
in ios_chrome_unified_consent_ui_tests (that run with Unified Consent disabled).

Bug: 960260

Change-Id: I0be1945ff290bd2fcbba44d64f733658c623b369
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599009
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659466}

Comments in ProfileDestroyer::DestroyProfileWhenAppropriate suggest
issues with OTR profile and RenderProcessHost lifetimes on ChromeOS.

We exclude the DCHECK that all guest view destruction callbacks have been
run by the time the profile is shutdown on ChromeOS. If there are outstanding
RenderProcessHosts, then we can't assert that the callbacks have been run.

Bug: 961607
Change-Id: I36d3d2797c7c03849f6242b67e67dea6a46b8b58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1606628Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659465}

This CL is a part of https://crrev.com/c/1602715.

The aim is to improve those tests by verifying the accounts stored by
OAuth2TokenService.saveStoredAccounts when doing a
OAuth2TokenService.updateAccountList.

Bug: 960281
Change-Id: Idab7319e1a5d7378bdb3e936efea4230e35904c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609824
Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Auto-Submit: Pâris Meuleman <pmeuleman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659464}

The piex.js.wasm script resource containing the Emscripten runtime and
the code to load the piex.out.wasm resource, were added to FilesApp in
CL:1597931. Add the piex.js.wasm to the FilesApp Image Loader manifest
to load it in a <script> tag in the Image Loader background page.

Tbr: lucmult@
Bug: 904630, 935285
Change-Id: Ibfa6cb73e28ca2bf9871cd8648389fcb67710e76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611617Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659463}

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

This probably went unnoticed because it's only used in some error-handling
paths.

Bug: none
Change-Id: I2707a1ceb9ba303454bfb0b622ad404340e0d0db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609827Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659461}

https://chromium.googlesource.com/angle/angle.git/+log/b783fbc79992..01cd5697760e


git log b783fbc79992..01cd5697760e --date=short --no-merges --format='%ad %ae %s'
2019-05-14 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src 2947e88f7938..e935dac9ef8a (1 commits)


Created with:
  gclient setdep -r src/third_party/angle@01cd5697760e

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

Change-Id: Ia99d351575f9635ff7ada0e517fdb343bd00d6ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610734Reviewed-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@{#659460}