GitLab

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8923650232d6..20f38b3d064b


Created with:
  gclient setdep -r src-internal@20f38b3d064b

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.


TBR=mmoss@chromium.org

Change-Id: Ifdef9937fc4acd5c007f458234cb949f709542df
Reviewed-on: https://chromium-review.googlesource.com/c/1315327Reviewed-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@{#604944}

This patch reduces the memory usage for NGBaselineList and
NGBaselineRequestList by making the types as index of an
array of LayoutUnit.

What to do when we add more baseline types is still TBD.
The rough plan is when adding baselines for Indic etc., we
can probably allocate rare_data pattern for 3 or more
baselines.

This change does not save memory for NGPhysicalBoxFragment
when there are no baselines, because NGBaselineList is the
same size as an empty Vector. It does save when there are
baselines, and also saves NGBaselineRequestList which is in
NGConstraintSpace.

All boxes within inline block, or boxes enclosed in legacy
layout have baselines and baseline requests. Also when
table/flex/grid are implemented in NG, their items and
descendents of items will have baselines.

At google.com, 19% (128/643) of box fragments have baselines.
20% (77/383) at amazon.com.

Change-Id: I6eb25a47528d92425880582ab6662944e9e8c125
Reviewed-on: https://chromium-review.googlesource.com/c/1312183Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604943}

We could have two DeleteSoon scheduled at the same time and cause
double deletion. Change LoginDisplayHostMojo::OnFinalize to use
ShutdownDisplayHost() so that they will be consolidated into one.

Bug: 900615
Change-Id: I2f2db9369079adc7d4cf24bb9ef65b15ebc79320
Reviewed-on: https://chromium-review.googlesource.com/c/1313740Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604942}

https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/46e2b4be31c7..b54e73475dd0

$ git log 46e2b4be3..b54e73475 --date=short --no-merges --format='%ad %ae %s'
2018-10-30 semenzato system_api: generate Go bindings for MetricsEvent
2018-10-30 dverkamp system_api: concierge: add DISK_TYPE_AUTO value
2018-10-26 norvez system_api: remove BiometricsManager constants
2018-10-25 iby system_api: Add proto fields to support dependency message in uninstall

Created with:
  roll-dep src/third_party/cros_system_api

Change-Id: I242902eea0e44a6c07984d30602ea81a463a7b49
Reviewed-on: https://chromium-review.googlesource.com/c/1312567Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604941}

https://swiftshader.googlesource.com/SwiftShader.git/+log/d0a4800..155f802

BUG=

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

Change-Id: I54f31ce39913d0956b5893daf3937a4f1a2c06e3
Reviewed-on: https://chromium-review.googlesource.com/c/1315167Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Commit-Queue: Nicolas Capens <capn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604940}

For structural nodes, still shows the "idPath", because our data model
does not allow mapping subpaths -> components.

Also fixes cell alignment in the infocard where titles were center
aligned over right-aligned values.

Bug: 880671
Change-Id: I5be0bb6b07aba20a9c49bffa4c14da45f8bb0599
Reviewed-on: https://chromium-review.googlesource.com/c/1313076
Commit-Queue: agrieve <agrieve@chromium.org>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604939}

Approved Intent to Ship:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/vTnSjFcPwNc/kkTX92hpBgAJ

BUG=846858
TBR=timvolodine@chromium.org

Change-Id: I48c81a799130b7d89157ba0795985fc2eb88ff17
Reviewed-on: https://chromium-review.googlesource.com/c/1291996
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604938}

When kStubCrosSettings switch is set, the logged in user is treated
as the owner of the device, and of the stubbed settings (which don't
need a real owner key).

This change moves this promotion of the user to the owner out of
ChromeUserManagerImpl and into CrosSettings. This untangles the two
classes slightly, and also it means that we can get rid of one
call to CrosSettings->Set, which is being removed.

See go/writepath for more background

Bug: 433840
Change-Id: I9f4a34b34d0160d220558e512b9d1c56b3e253a1
Reviewed-on: https://chromium-review.googlesource.com/c/1314491Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: A Olsen <olsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604937}

Using wpt-import in Chromium 8ad2ee9a.
With Chromium commits locally applied on WPT:
270d4abd "ServiceWorker: Add new WPT tests to make sure to update a registration with different script type and identical script content."


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:
mek@chromium.org:
  external/wpt/webmessaging

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: I8e51ba77dedbcbecabb85cfed0bcedc8940b6f48
Reviewed-on: https://chromium-review.googlesource.com/c/1314608
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#604936}

We used to limit this detection to internal keyboards, but
now we have external keyboards that have this newer layout as
well, and we should show the correct strings if any is connected.

BUG=b/118644994
TEST=Connect an external Brydge G-Type BT keyboard, and
     expect that the keyboard settings show the string
     "Launcher" instead of "Search"

Change-Id: I91892b9ac814dbe8b5ba6ec904ed7769e51eb507
Reviewed-on: https://chromium-review.googlesource.com/c/1313748Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604935}

This changes the video_capture service to use ServiceBinding for its
Service interface binding, eliminating reliance on ServiceContext as
well as EmebddedServiceInfo etc for content integration.

Bug: 891780
Change-Id: Ic1b89aa5487e230b4fafef2fdddf4b0e8e307b3c
Reviewed-on: https://chromium-review.googlesource.com/c/1311797Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#604934}

ReportExtensionsAndPluginsData policy blocks extensions and plugins report.
ReportSafeBrowsingData policy blocks Safe browsing data report.

Bug: 898673
Change-Id: Id2e2446ee342d13c07dcc79f150aa4baaedcb5c8
Reviewed-on: https://chromium-review.googlesource.com/c/1313329Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604933}

In https://crrev.com/bf23241073ef806810f2aa90bbb153b639239c81, I rewrote
UpdateViewportContainerSizes to be compatible with Blink generated
property trees. As part of this, we now make use of the outer viewport's
clip node. However, unlike the layer's bounds, the clip node's bounds
do not include the resize we perform to match the content width of the
page.

In WebViewImpl::ResizeAfterLayout, we resize the FrameView (and thus the
LayoutView) after we do a layout. We do this so that the layout viewport
is sized according to the minimum possible page scale (so pos: fixed
Elements are in the correct locations when the page is fully zoomed
out).

However, this isn't accounted for correctly in the ClipNode. This CL
applies the minimum scale to the clip bounds directly when computing the
clip as a result of URL bar movement. We should really fix the place
where the ClipNode is computed but this CL will need to be merged so
this is a minimal fix.

Note also, the ClipNode is correctly calculated with blink-gen-property-
trees enabled. This fix is thus only required when that's turned off.

Bug: 898757
Change-Id: I9c8ea517c2e98b6b2ac552b1ae64bd1675547614
Reviewed-on: https://chromium-review.googlesource.com/c/1313278Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604932}

https://skia.googlesource.com/skia.git/+log/13853a120d5a..30edaaac1da4


git log 13853a120d5a..30edaaac1da4 --date=short --no-merges --format='%ad %ae %s'
2018-11-02 brianosman@google.com Simplify and generalize alpha image extraction in PDF


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

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-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;master.tryserver.blink:linux_trusty_blink_rel
TBR=herb@chromium.org

Change-Id: Ic10f1c45c6bd20987d6c31c4c8d3b70ec5b89bb5
Reviewed-on: https://chromium-review.googlesource.com/c/1314103Reviewed-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@{#604931}

TopHosts() and HostRankIfAvailable() are unused, so removing.

BUG=none
TEST=none

Change-Id: I752a671e4e7b77546a7dff590c020a18d683e544
Reviewed-on: https://chromium-review.googlesource.com/c/1313050Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604930}

This reverts commit bf305c6a.

Reason for revert: cause crash

Original change's description:
> Remove TouchActionFilter::num_of_active_touches_
>
> This variable was added to test whether the touch start / end can be
> acked and released out of order or not. From the reading of the code,
> I don't think is true.
>
> This CL removes this variable, we will monitor crash reports to ensure
> this doesn't cause regression.
>
> To ensure the same behavior, we need a new variable, which is named
> |touch_sequence_in_progress_| in this CL. This is specifically for this
> scenario: we have received touch event ack for touch start, and then
> JS removes / adds touch event listener, which triggers a
> OnHasTouchEventHandlers call. In this case, we should not reset
> touch action if the |touch_sequence_in_pgoress_| is true. We have the
> unit test OnHasTouchEventHandlersReceivedAfterTouchStart to ensure
> this behavior.
>
> Bug: 900195
> Change-Id: I53c3141905b4e2a49ab6e62ea43335c4cee17c15
> Reviewed-on: https://chromium-review.googlesource.com/c/1307250
> Commit-Queue: Xida Chen <xidachen@chromium.org>
> Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#604260}

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

Bug: 901147
Change-Id: I4cd8387cd368eb6ca99010585ea872685953ac89
Reviewed-on: https://chromium-review.googlesource.com/c/1313841Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604929}

Add policy ReportExtensionsAndPluginsData.
Add policy ReportSafeBrowsingData

Bug: 898673
Change-Id: Ief72e4d7ab9aae2b31c199a2aaa4b2e346be7ef2
Reviewed-on: https://chromium-review.googlesource.com/c/1313512Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604928}

Update the profiles' validities for each major version to keep up with
the possible changes in the Autofill Profile Validator logic.
See: go/autofill-use-validation

Bug: 899783
Change-Id: Ie1c52df4c13a5579eb5265bda1eea19d02c5b123
Reviewed-on: https://chromium-review.googlesource.com/c/1311085
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604927}

https://chromium.googlesource.com/catapult.git/+log/971689c0597c..a6ef719b69f4


git log 971689c0597c..a6ef719b69f4 --date=short --no-merges --format='%ad %ae %s'
2018-11-02 cbruni@chromium.org [wpr] Add httparchive.go merge command


Created with:
  gclient setdep -r src/third_party/catapult@a6ef719b69f4

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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

BUG=chromium:896280
TBR=sullivan@chromium.org

Change-Id: I618bb6d1addf22744622d33888dd53a452625cf7
Reviewed-on: https://chromium-review.googlesource.com/c/1314104Reviewed-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@{#604926}

Because flaky.

PictureInPictureWindowControllerBrowserTest.EnterPictureInPictureThenFullscreen

TBR=mlamouri@chromium.org

Bug: 901235
Change-Id: Iab53371efe290a16b475c0a002c0561b184f8b08
Reviewed-on: https://chromium-review.googlesource.com/c/1315207Reviewed-by: vitaliii <vitaliii@chromium.org>
Commit-Queue: vitaliii <vitaliii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604925}

Currently we send the IPC to renderer in the BrowserPlugin-based case as well
which is hitting a NOTREACHED. This IPC is only meant to be used for frame-based
MimeHandlerViewGuest.

TBR=wjmaclean@chromium.org

Bug: 901289
Change-Id: Ib2efb7088d93c9339f1d920f1d3bf5c5a69718e4
Reviewed-on: https://chromium-review.googlesource.com/c/1314609Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604924}

This CL converted USB callings in WebUsbDetector to mojo interfaces
by introducing webusb_landing_page in UsbDeviceInfo.

Bug: 699790
Change-Id: I6352c35a7eb9090ef4d5cb3d2436b30216d76ec9
Reviewed-on: https://chromium-review.googlesource.com/c/1297747
Commit-Queue: Donna Wu <donna.wu@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604923}

Add metrics to to track the time taken first contentful paint
for pages that use whitelisted hosts for stale while revalidate.
This breaks the timings into whether the resource was loaded from
the network, cache, stale-cache loads.

BUG=348877

Change-Id: I4e710d6f52517a815d68d478584818501c10e0ea
Reviewed-on: https://chromium-review.googlesource.com/c/1297461
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604922}

https://webrtc.googlesource.com/src.git/+log/41f00de26bb1..56ef305b6767


git log 41f00de26bb1..56ef305b6767 --date=short --no-merges --format='%ad %ae %s'
2018-11-02 ossu@webrtc.org Move event logging of config into AudioSendStream.
2018-11-02 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 734e273d..e842ab5f (604373:604874)
2018-11-02 nisse@webrtc.org Delete _strnicmp. Uses replaced with abseil functions.


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

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I544e1cc5b76fde583988db3a8999853dbb4c72c3
Reviewed-on: https://chromium-review.googlesource.com/c/1314106Reviewed-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@{#604921}

TaskScheduler requires the FeatureList, so it needs to be moved
from CastBrowserMainParts::PreCreateThreads() to an earlier point,
CastMainDelegate::PostEarlyInitialization().

The creation of the "singleton" FieldTrialList instance also needs
to be moved to CastMainDelegate::PostEarlyInitialization(), since the
FeatureList initialization depends on the FieldTrialList. Its
ownership was transferred from BrowserMainParts to CastMainDelegate.

A new CastFeatureListCreator class holds ownership of the service
while the browser process isn't started.

Bug: 887459
Change-Id: I4bcd60720518807e2089ec99a3f7db3e647203d6
Reviewed-on: https://chromium-review.googlesource.com/c/1308096
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Reviewed-by: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604920}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/643fe6108096..8923650232d6


Created with:
  gclient setdep -r src-internal@8923650232d6

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.


TBR=mmoss@chromium.org

Change-Id: I7e93d631e82dafb4a4b7d8ba1d31acfb045a4159
Reviewed-on: https://chromium-review.googlesource.com/c/1314105Reviewed-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@{#604919}

Outlining in LLD creates many symbols with names OUTLINED_FUNCTION_0,
OUTLINED_FUNCTION_1, etc. that appear many times. Problems:
* Unrelated symbols can share the same name. If object path information
  is available in the .map file (true for arm64 without ThinLTO), then
  SuperSize would run 10x as long because these paths get joined in an
  O(n^2) fashion.
* In nm output, an address can have many OUTLINED_FUNCTION_* symbols,
  which adds to the bloat.

This CL adds to SuperSize outlining support to solves the problems above.
Details:
* link_map_parser.py: (for LLD, and also Gold for testing) Detect
  OUTLINED_FUNCTION_* and reassign the name to '** outlined function'.
  The '*' prefix labels these symbols as placeholders, so these
  symbols will be ignored by nm results from .o files, and no object
  path joining occurs.
* nm.py: For the nm call to the main ELF file, combine multiple
  OUTLINED_FUNCTION_* with the same address into a single symbol, and
  assign the name to '** outlined function * (count)'. If combination
  takes place, then "forced passing" occurs, i.e., the name will
  always be passed (rather than discarded to save space) to
  |names_by_address|.
* archive.py: Updated to reconcile the two sources of
  '** outlined function' symbols.

Outlined functions can share address with named symbols. Due to the
combining in nm.py, this causes number of aliased symbols to decrease
for affected named symbols (and increases PSS).

'** outlined function' symbols can have object_path assigned, but the
data are obtained from .map files only, since these symbols are ignored
for nm results from .o files. Furthermore, if an outlined function
symbol shares an address with any other such symbol (as found by nm
results for the main ELF file), then it won't have object_path assigned
(since "forced passing" above causes _AddNmAliases() to process the
symbol, but this discards object_path data from .map files).

Bug: 891061
Change-Id: Ie0109c7fc876749c10a87b5a7673af2be49d38c4
Reviewed-on: https://chromium-review.googlesource.com/c/1312561Reviewed-by: Samuel Huang <huangs@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604918}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/fa338454..879aea82

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I968256e6b1db2ce1a5f36b5da7b8bf55328079f2
Reviewed-on: https://chromium-review.googlesource.com/c/1314147Reviewed-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@{#604917}

Disabling window maximize tests on Mac for Chrome v69

Change-Id: Ide707ac877e3f94b32d48ad27400aba41782a19f
Reviewed-on: https://chromium-review.googlesource.com/c/1314137Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604916}

Bug: none
Change-Id: I92eeb20b32a1127e6b98a7b23d8e4bd40a3e1506
Reviewed-on: https://chromium-review.googlesource.com/c/1313563Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604915}

Fixes imported here:
https://chromium-review.googlesource.com/c/1314128

Spec change:
https://github.com/w3c/csswg-drafts/issues/2394

TBR=szager@chromium.org

Bug: 884588
Change-Id: I4e1c9537122817afb9ebe03ad70290a0558f582c
Reviewed-on: https://chromium-review.googlesource.com/c/1314631Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604914}

Payment request returns details that are detached from profile.
In order to use them by autofill a profile is needed, which we
now create on the fly.


Bug: 806868
Change-Id: Ic5ef1b4767b0978d2ef47557a5c10b8a2e7c5cfb
Reviewed-on: https://chromium-review.googlesource.com/c/1304518
Commit-Queue: Lukasz Suder <lsuder@google.com>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604913}

Bit of a cleanup accesory to crrev.com/c/1308043: a new pair
of private methods (StartListeningForDidProcessTask() and
StopListeningForDidProcessTask() ) are added. They work together
with the associate renamed flag
s/finalize_frame_scheduled_/listening_for_did_process_task_/
to listen for ProcessTask events (WillProcessTask/DidProcessTask).

This is a cleanup of things in preparation for the next CL
in the chain: crrev.com/c/1308043.

No new functionality intended.

Bug: 839970
Change-Id: I0bad9e3bfc80b02865c34ba4c20d37f71ecb83a9
Reviewed-on: https://chromium-review.googlesource.com/c/1308754Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604912}

This reverts commit 36713b50.

Reason for revert: Causes Chrome to crash on power.typical_10_mobile Rotating earth test.

Original change's description:
> NavigationPredictor: Skip anchor elements that belong to an ad frame
> 
> At OnLoad event, the renderer notifies browser process of the
> anchor elements in the viewport. The browser uses this information
> to predict the navigation probability of each of these anchor
> elements.
> 
> This CL changes the logic in the render side to skip reporting
> of elements that are part of ad frames since we expect these
> to be clicked less often.
> 
> Change-Id: Ia131ac301acda317e7618ac206f4bda60c39e5cf
> Bug: 899339
> Reviewed-on: https://chromium-review.googlesource.com/c/1300682
> Reviewed-by: Steven Holte <holte@chromium.org>
> Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Commit-Queue: Tarun Bansal <tbansal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#604738}

TBR=kinuko@chromium.org,holte@chromium.org,tbansal@chromium.org,ryansturm@chromium.org

Change-Id: Ifa21f582007d7f50917e66a94ea905cf3a095902
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 899339
Reviewed-on: https://chromium-review.googlesource.com/c/1315208Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604911}

For some reason we created a new AttachContext entering a ShadowRoot for
AttachLayoutTree. If the shadow host was display:contents we would lose
the previous_in_flow from the shadow tree checking the need for
whitespace LayoutObject for shadow host siblings.

Created a common space-separated words expectation for css.

Bug: 901323
Change-Id: Ib2fa54d55923c0497ff8e96c5010e68b01570881
Reviewed-on: https://chromium-review.googlesource.com/c/1314589Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604910}

Real-world crashes have been caused by WebStateList being nil in a
WebStateListObserver callback. Logically, this should not happen since
the WebStateList should be guaranteed to be alive until all the
observer callbacks have completed. That is unfortunately false.
We believe there could be some compiler optimization that is causing
the WebStateList to be destructed before the callback is completed.

Bug: 877792
Change-Id: I0e7c5cc843d29c6d78349f1fe2f33d7317c20db1
Reviewed-on: https://chromium-review.googlesource.com/c/1309750
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604909}

Apparently there also is ubsan_minimal runtime which we do not use:
https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#minimal-runtime.

It's fairy small though:

20K	libclang_rt.ubsan_minimal-i386.a
20K	libclang_rt.ubsan_minimal-i386.so
24K	libclang_rt.ubsan_minimal-x86_64.a
4.0K	libclang_rt.ubsan_minimal-x86_64.a.syms
20K	libclang_rt.ubsan_minimal-x86_64.so


Bug: 870331
Change-Id: I280fa27fce61095bffe5e91fed92245c75d051db
Reviewed-on: https://chromium-review.googlesource.com/c/1313756Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604908}

As MessageLoopForUI and IO are not part of MessageLoopImpl (they are
just talking to the relevant pump), move them to the main file.

R=gab@chromium.org
BUG=891670

Change-Id: Ifdbb7916c43e8c51331a34b73902d58a3d8a9ecb
Reviewed-on: https://chromium-review.googlesource.com/c/1313589Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604907}

As UsbChooserContext stores all device infos available to the device
manager, other storages could be reduced by only keeping guid and
getting the details from UsbChooserContext by GetDeviceInfo() method.

Bug: 699790
Change-Id: I42f19a530fcf030cb896b3b26f218fe019b77e33
Reviewed-on: https://chromium-review.googlesource.com/c/1296313
Commit-Queue: Donna Wu <donna.wu@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604906}

https://webrtc.googlesource.com/src.git/+log/d4a68bd932a1..41f00de26bb1


git log d4a68bd932a1..41f00de26bb1 --date=short --no-merges --format='%ad %ae %s'
2018-11-02 titovartem@webrtc.org Fix chromium roll
2018-11-02 nisse@webrtc.org Delete rtc::Pathname


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

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:NONE
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I34867ce7d77f0c768818b189572465d75ff481a8
Reviewed-on: https://chromium-review.googlesource.com/c/1314102Reviewed-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@{#604905}