GitLab

Another case SelectionPopupController gets a native->Java
flow handed over from ContentViewCore. The feature is relevant
to selection controller, which is now is fully capable of
taking care of it without relying on ContentViewCore thanks
to https://crbug.com/c/956786.

Not related, but did some clean up in content_view_core.h
for method declarations left unused.

Bug: 598880
Change-Id: I5010644a67021632b1e2625167e02c3c4ab947d8
Reviewed-on: https://chromium-review.googlesource.com/963155Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543557}

Bug: 812828
Change-Id: I41b5880225b500cebcbf1581c18538e686f9d9c0
Reviewed-on: https://chromium-review.googlesource.com/933109
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543556}

This CL resets the filter_ member in the site data handler (c++) so that
the filter will be reapplied when revisiting the page.

Bug: 820816
Change-Id: Id710d8f6b9ec35f8ee69088dbbd8d8d9b3691c38
Reviewed-on: https://chromium-review.googlesource.com/964986Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543555}

ARC++ gets its device scale factor from the default ManagedDisplayMode.
When display zoom is enabled, we only have 1 display mode for the
internal display. This display mode was not set as the default until
now, causing ARC++ to get an invalid device scale factor.

Bug: 790723
Change-Id: Ia86a3c22edb21ea3d0ced63f31992cca3e700ad6
Component: Managed Display Mode, Device scale factor, display zoom
Reviewed-on: https://chromium-review.googlesource.com/964795Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543554}

The summary and background mode use the same set of MDPs now.
So, remove duplicate list.

BUG=730783

Change-Id: I3568d797d5bab3d36df658feb22df28d8ea786a4
Reviewed-on: https://chromium-review.googlesource.com/961554
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: Hector Dearman <hjd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543553}

Previously, it would only take effect when a single feature was
enabled on the study. The new logic would associate with all the
features.

Bug: 816696
Change-Id: Ide5ace721ade5e78f8743b11a96998d3b08ded46
Reviewed-on: https://chromium-review.googlesource.com/963087
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543552}

This makes our merge guidelines more permissive for feature work
which is gated behind a flag.

Change-Id: I1b65711006cf04e754570d55c16a12b51ed782f5
Reviewed-on: https://chromium-review.googlesource.com/958035Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Alex Mineer <amineer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543551}

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I0a7fedfe646e43d4ba92ae1361411e7b4c84ab0a
Reviewed-on: https://chromium-review.googlesource.com/964886Reviewed-by: edchin <edchin@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543550}

In some cases extreme output canvas sized were causing failed
allocations and incomplete framebuffers, which made the ImageLayerBridge
choke. This patch both clamps the backbuffer size to the max texture
size and, if an incomplete framebuffer is detected, produces black 1x1
images for the ImageLayerBridge to consume instead of attempting to pass
the texture that failed to allocate.

Bug: 814460
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Idba50e08052767360423018e06bc65f1f87c4d14
Reviewed-on: https://chromium-review.googlesource.com/964796Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543549}

When the root surface changes, we cannot draw to the display until a surface
activates. This CL stops draws (and BeginFrames) until activation. If a root surface is never
submitted then the display will not listen for BeginFrames.

Bug: 821940
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I749c0ca8e85a3dbc7eccaa0799add81afb15beb9
Reviewed-on: https://chromium-review.googlesource.com/964595Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543548}

Change-Id: Ie2ad7d92c74e45a4a59be8569758f9217909eab3
Reviewed-on: https://chromium-review.googlesource.com/961582Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Paul Irish <paulirish@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543547}

BUG=https://github.com/GoogleChrome/lighthouse/issues/4745

Change-Id: I959f6c7fdff1427b60dcac482773902c6fda1bc0
Reviewed-on: https://chromium-review.googlesource.com/961540Reviewed-by: Paul Irish <paulirish@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Patrick Hulce <phulce@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543546}

https://chromium.googlesource.com/catapult.git/+log/ee4c7175f67b..36d08eec1a07

$ git log ee4c7175f..36d08eec1 --date=short --no-merges --format='%ad %ae %s'
2018-03-15 dtu [pinpoint] Generalize "configuration" to be a set of argument presets.

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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=sullivan@chromium.org

Change-Id: I1abf222433c05fa1ee45b6feb7c96209d1a60650
Reviewed-on: https://chromium-review.googlesource.com/965101Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543545}

tbr=estade@chromium.org

Bug: 822470
Change-Id: If9f4edf28d232113f6da357c7646feeef63d72cc
Reviewed-on: https://chromium-review.googlesource.com/965256Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543544}

These tests were disabled for simulators for being flaky under multiple
simulators mode. Now the mode is turned off for these tests, they should
be re-enabled again,  but still failing due to issue 821490.

Bug: 814990
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ie75bfa9ed9ba14552123199ff2d202477ae12457
Reviewed-on: https://chromium-review.googlesource.com/961595
Commit-Queue: Menglu Huang <huangml@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543543}

Media used to rely on SharedCompositorWorkerContextProvider,
therefore it needed to lock and unlock the GLContext everytime
it needed to do a GL operation.

Later the context has been replaced with one created
specifically for media, and that is accessed only on the media
thread. The locks/unlocks were not removed though.

This patch removes all the locks/unlocks and make sure all the
operation on the media context are happening only on the
media thread.

Bug: 580386
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ie524c1c6a56a4f16171f2390d471a023a0e76a0b
Reviewed-on: https://chromium-review.googlesource.com/959432Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543542}

This will allow us to determine how much magic window mode is used vs
presentation by looking at the ratio of this UseCounter vs presentation
UseCounter.

TBR=vollick@ for web_feature.mojom, which doesn't need owner review.
BUG=776086

Change-Id: I6e28433a00a8dbb9be3315d926d8f2b225be5b3e
Reviewed-on: https://chromium-review.googlesource.com/752079Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543541}

This pulls the two event dispatch related functions out of
EventProcessorDelegate into a new interface. I'm doing this as a
precursor to moving the event dispatch related code out of
WindowManagerState.

BUG=none
TEST=none

Change-Id: I249581a109e38f535d1b48ebe0ebf9785738dbc2
Reviewed-on: https://chromium-review.googlesource.com/964783
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543540}

https://skia.googlesource.com/skia.git/+log/e11d7932940b..af18f22da6c5

$ git log e11d79329..af18f22da --date=short --no-merges --format='%ad %ae %s'
2018-03-15 scroggo Make get_images_from_skps always return success
2018-03-15 reed rm guard for google3
2018-03-15 bsalomon Cleanup SkImage YUV texture factories.
2018-03-15 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 0b0dcbc1c..44a73fcfb (2 commits)

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=stephana@chromium.org

Change-Id: Ia4f80a7919d5fba0f908a5784f59a7aa8cee8d64
Reviewed-on: https://chromium-review.googlesource.com/964987
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543539}

Mostly range-based for loops for iterators

Change-Id: I12d18dd5cab78fed9279597a286efa07331860da
Reviewed-on: https://chromium-review.googlesource.com/938955
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543538}

This is to debug an issue with bit increased SW timeouts in
StopLoadingInBackground experiment.

Bug: 790903
Change-Id: I89edec7f1b077e4ecd35256ecc09c6083db14879
Reviewed-on: https://chromium-review.googlesource.com/955680
Commit-Queue: Shubhie Panicker <panicker@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543537}

Also //mojo/edk/embedder:headers -> //mojo/edk

This makes more sense.

There's some random GN autoformatting here as well.

TBR=sky@chromium.org

Bug: None
Cq-Include-Trybots: luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I3ade31b7f4b127f341fd114acc5c092bcba22659
Reviewed-on: https://chromium-review.googlesource.com/963548
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543536}

- Adds expand/collapse functionality.
- Adds contextmenu functionality (Open All and Hide For now).
- Adds a tapGesture recognizer for headers.

Video:
https://drive.google.com/open?id=1LwJCMrUlNmJ73O_SWHEpImBqaEh4M1hv

Bug: 819462
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Idc51238b5cfb205f3150d33364efad83868c7333
Reviewed-on: https://chromium-review.googlesource.com/958099
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543535}

Fixes two things in the VR auto bisect script:
1. Sets an empty list as the default for the checkout override arg, as
   otherwise it was trying to iterate over None when not set.
2. Ensure that the VR APKs are downloaded during syncing.

Change-Id: I2191accdc23fd858b0588c7772785ce4a95edc6a
Reviewed-on: https://chromium-review.googlesource.com/965115Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543534}

The underflow was occurring during subtraction of two uints, before the
saturated_cast could fix the result.

Bug: 812346
Change-Id: I08acf91e137880fe7aba0d41f8ea362c9f81315c
Reviewed-on: https://chromium-review.googlesource.com/955908Reviewed-by: Primiano Tucci <primiano@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543533}

Using wpt-import in Chromium 66d1e9a8.

Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/13873

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
igrigorik@chromium.org, yoav@yoav.ws:
  external/wpt/preload

TBR=lukebjerring

No-Export: true
Change-Id: Ib362952573de1b6d1fc4f136ba82575d4486f349
Reviewed-on: https://chromium-review.googlesource.com/964794
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543532}

https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/4468d4967f5d..02ec9ce5a9bc

$ git log 4468d4967..02ec9ce5a --date=short --no-merges --format='%ad %ae %s'
2018-03-13 wolenetz Updating build configs for M67 roll.
2018-03-13 wolenetz Update build_ffmpeg.py's sysroot name for M67
2018-03-13 wolenetz Remove deprecated av_register_all from ffmpeg.sigs
2018-03-13 wolenetz Copy [de]muxer, codec and parser lists into configs
2018-03-12 wolenetz Update chromium patches README
2018-03-12 vdixit avformat/hlsenc: fix for zero EXTINF tag duration
2018-03-12 matthieu.bouron avcodec/mediacodecdec_common: make INFO_TRY_AGAIN trace messages more consistent
2018-03-10 aman avcodec/mediacodecdec: add debug logging around hw buffer lifecycle
2018-02-27 michael avcodec/nuv: rtjpeg with dimensions less than 16 would result in no decoded pixels thus reject it
2018-02-27 michael avcodec/nuv: Check for minimum input size for uncomprssed and rtjpeg
(...)

Created with:
  roll-dep src/third_party/ffmpeg

Includes removal of FFmpegGlue::InitializeFFmpeg() because
av_register_all is no longer needed (and is deprecated in FFmpeg).

BUG=803898, 772699, 786793, 791237, 791349, 795653, 796778, 800123, 817338

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I94ccecab95831174a3bae6e9a8422e10bfec8e85
Reviewed-on: https://chromium-review.googlesource.com/964248Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543531}

These classes represented Bluetooth Classic connections, which are no longer used.

R=khorimoto@chromium.org

Bug: none
Test: none
Change-Id: I8223f3afca936cf3711f4a73334e9d8aed80d9e1
Reviewed-on: https://chromium-review.googlesource.com/964624
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543530}

Bug: 818902
Test: added test coverage
Change-Id: Ie5c0edf874c50be60b48b37833fcf1e8991e5728
Reviewed-on: https://chromium-review.googlesource.com/963089
Commit-Queue: Qiang Xu <warx@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543529}

As a precursor to moving SDK thunks around and rewiring them, this
fixes some of the weird layering within //mojo/edk.

Namely this introduces a new //mojo/edk target to subsume the role
of //mojo/edk/system (aliased for now to avoid churn), and splits out
a source_set (//mojo/edk:core) for the bulk of the EDK impl with no
linkage dependencies on //mojo/public.

A follow-up patch (https://crrev.com/c/963548) will get rid of the
alias targets.

Bug: 822034
Change-Id: I6b45ce6e8bb9b3a5392ae8e5cdfb61bbc4761769
Reviewed-on: https://chromium-review.googlesource.com/963766
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543528}

We already were silencing most of this via stdout filtering, but there
are still some third-party libraries that were showing warnings. E.g.:

Warning: can't write resource [META-INF/maven/com.google.guava/guava/pom.xml] (Duplicate zip entry [espresso-core-release-no-dep.jar:META-INF/maven/com.google.guava/guava/pom.xml])

This change tells ProGuard to ignore these files, rather than filtering
the resulting errors

Change-Id: I288507de1f2c5576fbb0fea8bfebb189b2603c92
Reviewed-on: https://chromium-review.googlesource.com/963699Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543527}

This reverts commit 93d6eba0.

Reason for revert: Failing webkit_unit_tests:
  RenderedPositionTest.PositionInScrollableRoot
  RenderedPositionTest.PositionInScroller/
on https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/4730

Original change's description:
> Make touch handles relative to scrolling contents
> 
> Selection bounds are sent from Blink to CC as part of a commit cycle so
> that we can draw touch handles for it. Currently, the selection bounds
> are relative to the main graphics layer of a CompositedLayerMapping. In
> the case of a scroller, this will be its clip rect - rather than its
> scrolling contents layer. Unfortunately, this means that scrolling on
> the compositor isn't applied as part of the ToScreen transformation on
> the selection bounds so scrolling wont update the selection bounds
> location until another Blink commit. This went unnoticed until now
> because the root layer was not considered a scroller. The page would
> paint into a document-sized layer and the compositor would provide extra
> scrolling layers to handle frame scrolling. In this configuration, the
> ToScreen transformation from the root layer does include the scroll
> offset.
> 
> Now that root layer scrolling has been turned on, frame scrolling works
> much the same as other scrollers. Thus, this shortcoming is seen on
> frame scrolling also.
> 
> The solution in this CL is to move the selection bounds rect to be
> relative to the scrolling contents layer - if one exists. The ToScreen
> transformation done in CC will correctly compensate for any scroll
> offset applied in the compositor and touch selection handles stick to
> the selection as its scrolled. For the CC side, see
> ComputeViewportSelectionBound in layer_tree_impl.cc
> 
> Bug: 812048
> Change-Id: I219ac3209d334ac91e9c13ffaaa51cbc9db57886
> Reviewed-on: https://chromium-review.googlesource.com/963006
> Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
> Commit-Queue: David Bokan <bokan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543436}

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

Change-Id: I7ed3e4a8494caf31772af6eae2b25e3d4d13a330
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 812048
Reviewed-on: https://chromium-review.googlesource.com/965281Reviewed-by: Greg Levin <glevin@chromium.org>
Commit-Queue: Greg Levin <glevin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543526}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5d11b541fc9e..ceb1b20c4313

$ git log 5d11b541f..ceb1b20c4 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src-internal


The AutoRoll server is located here: https://src-internal-chromium-roll.skia.org

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=mmoss@chromium.org

Change-Id: I6fac62094790ce1a52606ececcd51b9f954c01f1
Reviewed-on: https://chromium-review.googlesource.com/964888
Commit-Queue: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: src-internal-chromium-autoroll <src-internal-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543525}

Now that the web font timing issue for WPT in Blink has been fixed
(https://crbug.com/507054), these tests should no longer be flaky.
Remove the expectations.

Bug: 582836
Change-Id: I88f94b0f9133c8c787a358f00f06a76382e7d26e
Reviewed-on: https://chromium-review.googlesource.com/962704Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543524}

https://chromium.googlesource.com/angle/angle.git/+log/41918387cc52..44a73fcfbe2d

$ git log 41918387c..44a73fcfb --date=short --no-merges --format='%ad %ae %s'
2018-03-06 brandon1.jones Always Invalidate Vertex Attribute Translation

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=cwallez@chromium.org

Change-Id: Ie68f2a687b31a049677df2024554b93523a5323e
Reviewed-on: https://chromium-review.googlesource.com/964803Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543523}

The background page only existed to support BT Classic flow, which is
now gone.

R=tengs@chromium.org

Bug: none
Test: none
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4af74256299656a119507a209b875a213226fadd
Reviewed-on: https://chromium-review.googlesource.com/964909Reviewed-by: Tim Song <tengs@chromium.org>
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543522}

HttpCache::Transaction::ResetPartialState dooms the current entry, and
goes back to creating a new entry for this request. In case of parallel
validation, if the first request is a full request and has written some
part of the response to the cache, then this second transaction would
create the range header with as many bytes as the written response even
on dooming the current entry which is incorrect.
This CL fixes it by restoring the original range header on this path.

RangeGET_ParallelValidationCouldntConditionalize
Also manually verified the test case reported in the bug.

TEST: net_unittests --gtest_filter=HttpCache.
Bug: 820599
Change-Id: I4e57003193873e433c3b503b9fc20a843f28c4da
Reviewed-on: https://chromium-review.googlesource.com/959450Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Commit-Queue: Shivani Sharma <shivanisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543521}

Disabling pending a resolution to crashes observed in the associated
bug.

This change also removes the unused
GetSamplingParamsForCurrentProcess function and adapts
IsProfilerEnabledForCurrentProcess to operate on the current process
and specified thread.

The call to IsProfilerEnabledForCurrentProcess is also removed
from SetServiceManagerConnectorForChildProcess since that function is
only invoked in processes supporting the profiler.

Bug: 774682
Change-Id: Ibbc6f1bd9348ba09a3ee4db2e1595411617f1ccd
Reviewed-on: https://chromium-review.googlesource.com/962937
Commit-Queue: Mike Wittman <wittman@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543520}

Bug: None
Test: compiles & trybots
Change-Id: I29d5c39a018e6a2ddc0df3e123780f0bffd7aa99
Reviewed-on: https://chromium-review.googlesource.com/963650
Commit-Queue: Qiang Xu <warx@google.com>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543519}

This is a no-op because the BT classic flow is gone.

R=khorimoto@chromium.org

Bug: none
Test: none
Change-Id: I9a3c86e5c2fc7cacbf3d301dcae233ef5c04bfc8
Reviewed-on: https://chromium-review.googlesource.com/963308
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543518}