GitLab

This CL adds an argument option to print out debug info for diagnostics.

Bug: 801231
Change-Id: I53b23c6569c9938ef4c5b5a786ceaeee751ffc5d
Reviewed-on: https://chromium-review.googlesource.com/871506Reviewed-by: Abhishek Arya <inferno@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532530}

Change-Id: I31e3e705624cab5cd5005fe46f3c88d2517c549d
Reviewed-on: https://chromium-review.googlesource.com/887284Reviewed-by: Bartosz Fabianowski <bartfab@chromium.org>
Commit-Queue: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532529}

This reverts commit f9a22f3e.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Oilpan: Immediatelly promptly free objects.
> 
> This CL brings the following changes to promptly freeing and coalescing:
> 1) Promptly freed objects on already swept pages are immediately added to the free list.
> 2) For promptly freed objects on not already swept pages we only clear the mark bit.
> 3) The promptly_freed_size_ counter is explicitly set to 0 before sweeping because sweeping will take care of coalescing as well.
> 4) The dead bit is removed.
> Note that coalescing before sweeping completed can not happen.
> 
> Future outlook: As a next step we will evaluate if we need coalescing and if we need it we have to make it jank friendly.
> 
> Bug: chromium:804279, chromium:633030
> Change-Id: I35dfae80ae0e7ed6cfbc91877d97d0b5fc26498e
> Reviewed-on: https://chromium-review.googlesource.com/873974
> Commit-Queue: Hannes Payer <hpayer@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532509}

TBR=haraken@chromium.org,hpayer@chromium.org,mlippautz@chromium.org

Change-Id: I868bc9b51c18a546994de93a3a8ef80362b0ba19
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:804279, chromium:633030
Reviewed-on: https://chromium-review.googlesource.com/891640Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532528}

Setting the pan attribute will set the value immediately instead of
dezippering from the current value to the new value.

Chromium Feature: https://www.chromestatus.com/features/5287995770929152
Intent to ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/YKYRrh0nWMo/aGzd3049AgAJ

Bug: 752985
Test: StereoPanner/dezipper.html
Change-Id: I13815d7cb3a6d4ea93dd8f0f1bab739e6768e561
Reviewed-on: https://chromium-review.googlesource.com/607028
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532527}

All socket writes need to be annotated with traffic annotation tag.
This CL adds this requirement to the API.

Bug: 721401
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Iee211a7812ba074f2788c879d0bc4b715e178fde
Reviewed-on: https://chromium-review.googlesource.com/881425Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Randy Smith <rdsmith@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532526}

https://chromium.googlesource.com/angle/angle.git/+log/d1434c048145..e4741fd0f2bc

$ git log d1434c048..e4741fd0f --date=short --no-merges --format='%ad %ae %s'
2018-01-25 lucferron Vulkan: Begin implementing caps mappings

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;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
TBR=ynovikov@chromium.org

Change-Id: Id100844c51b2eb57e54b82ba0e1cdadc2db93713
Reviewed-on: https://chromium-review.googlesource.com/891300
Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org>
Reviewed-by: angle-deps-roller . <angle-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532525}

Remove dezippering so that when the gain value is set, the output gain
immediately snaps to the value, instead of exponentially approaching
the target value.

Chromium Feature: https://www.chromestatus.com/features/5287995770929152
Intent to ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/YKYRrh0nWMo/aGzd3049AgAJ

Bug: 555647
Test: Gain/dezipper.html
Change-Id: I31c2b067c9eeade4127195b2eb9bc3b716f308b5
Reviewed-on: https://chromium-review.googlesource.com/602604Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532524}

This is a content/ concept that can remain soley in content/,
and it turns out the zygote doesn't do anything with it.

Change-Id: I91f81af707532c81f6fcc0d2fce6eea233ba3c27
Reviewed-on: https://chromium-review.googlesource.com/887822
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532523}

Using wpt-import in Chromium b04cb83b.
With Chromium commits locally applied on WPT:
9f32e9c0 "S13nServiceWorker: Add tests for network fallback for navigations with request bodies"


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

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

TBR=leon.han@intel.com

No-Export: true
Change-Id: I62cd59f2f13776df7201c3398ac643cef9cd8d0a
Reviewed-on: https://chromium-review.googlesource.com/889773
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@{#532522}

https://skia.googlesource.com/skia.git/+log/cca86f386cfd..11e5bff1594c

$ git log cca86f386..11e5bff15 --date=short --no-merges --format='%ad %ae %s'
2018-01-29 ethannicholas workaround for Intel SPIR-V OpCompositeConstruct bug
2018-01-29 angle-skia-autoroll Roll skia/third_party/externals/angle2/ d1434c048..e4741fd0f (1 commit)

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;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
TBR=bungeman@chromium.org

Change-Id: I1ef5368b90cf1e275c819defc640d7b41cbbf227
Reviewed-on: https://chromium-review.googlesource.com/891422
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@{#532521}

Revert "Cros splitscreen: Disable the splitscreen for M65 stable but keep it enabled for all other channels."

This reverts commit ddccd3f6:
https://chromium-review.googlesource.com/c/chromium/src/+/869196

M65 has been cut. This CL is no longer needed. Revert it.

Bug: 800501
TBR: oshima@chromium.org
Change-Id: I1943f27874fa83b67ca7d42e1b292f93f52f86a0
Reviewed-on: https://chromium-review.googlesource.com/887878Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532520}

Patch https://chromium-review.googlesource.com/c/chromium/src/+/742162
got reverted because it caused cc_unittest failure on CFI bot. This
patch fixed the bug.

Commit message from the original patch:

The current cc/animations logic assumes a single animation has a single
keyframe effect and can only affect a single layer. To enable animations
with multiple keyframe effects, cc::AnimationPlayer need to support
multiple AnimationTickers each corresponding to one keyframe effect.

Currently there is a 1:1 relationship between AnimationPlayer and
AnimationTicker. This patch is to extend it to 1:n. Here is a summary of
changes:
- Introduce a sub-class of AnimationPlayer, a.k.a
SingleTickerAnimationPlayer, to handle the existing logic (single
effect). SingleTickerAnimationPlayer owns only one AnimationTicker as
the AnimationPlayer does today.
- Currently a AnimationTicker is created upon creating AnimationPlayer.
In this patch, tickers are created separately and added to the player
afterwards. Tickers that the player owns may belong to different targets
therefore the player needs to coordinate with AnimationHost regarding
this situation.
- Adjust existing unit tests according to the changes above.

Bug: 767043
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: If21bad1285c35bbc048fef6b619c8272c0760551
Reviewed-on: https://chromium-review.googlesource.com/890724Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532519}

The domain cdn.ampproject.org and its subdomains should be preloaded for
HSTS and pin to a Google certificate chain.

TBR=palmer@chromium.org

Change-Id: I5c0edd88b9cda350ab4c77d59f3d8b650d674518
Reviewed-on: https://chromium-review.googlesource.com/890045Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Commit-Queue: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532518}

//chrome/browser correctly lists //chrome/common:service_process_mojom
in its public_deps. However, //chrome/browser/extensions and
//chrome/browser/ui are listed in allow_circular_includes_from, allowing
them to include headers from //chrome/browser without a dependency. Add
explicit dependencies from //chrome/browser/extensions and
//chrome/browser/ui to //chrome/common:service_process_mojom.

Bug: 805916
Change-Id: I83c2c7588e8056d413b9cccc8f5eceeb203986d7
Reviewed-on: https://chromium-review.googlesource.com/890686
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532517}

Original CL: https://chromium-review.googlesource.com/886863

Fix:
- Suppress unused resources for clank/ widgets

BUG=799070,806060
TBR=nyquist@chromium.org,twellington@chromium.org

Change-Id: Id42c5a626f4a0754bea3d4db7a10af9756c0002d
Reviewed-on: https://chromium-review.googlesource.com/891339
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532516}

This change moves Cocoa-only browser and test source files into variables, to
reduce merge conflicts while these files get integrated into the Views browser
builds as well.

Bug: 802257,804950
Change-Id: I123b778fb7614afc20a50a800eab5ae2a6290b24
Reviewed-on: https://chromium-review.googlesource.com/889792
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532515}

See https://bugs.chromium.org/p/chromium/issues/detail?id=722928#c72
which says that FALLTHROUGH is intended here.

This CL was uploaded by git cl split.

R=tdresser@chromium.org

Bug: 177475
Change-Id: I3555a1bb32d6b7ec5a2f68dd13266da2e48af62c
Reviewed-on: https://chromium-review.googlesource.com/890429Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532514}

This reverts commit 09ef7a92.

Reason for revert: the original revert did not fix ProcessManagerBrowserTest.NestedURLNavigationsToExtensionBlocked failing: https://bugs.chromium.org/p/chromium/issues/detail?id=806684#c8 

Original change's description:
> Revert "Use SCANOUT_* usage in GpuMemoryBufferVideoFramePool"
> 
> This reverts commit b6486594.
> 
> Reason for revert: speculative revert for fixing browser_tests
> failure on Win (32) Tests bot.
> 
> ProcessManagerBrowserTest.NestedURLNavigationsToExtensionBlocked started to fail
> continuously after the CL. I'm not fully confident of the 
> relationship between the failure and this change, but trying to
> revert to see if it helps. 
> 
> 
> Original change's description:
> > Use SCANOUT_* usage in GpuMemoryBufferVideoFramePool
> > 
> > Currently GpuMemoryBufferVideoFramePool allocates buffers with
> > GPU_READ_CPU_READ_WRITE usage. This means these buffers won't be used for
> > scanout (no fb added on CrOS).
> > 
> > This CL simply changes the usage used when allocating buffers to
> > SCANOUT_CPU_READ_WRITE, in this way this buffers will be created for
> > scanout, if possible.
> > 
> > Note that SCANOUT implies GPU_READ, meaning that in case the allocation
> > of the buffer for scanout will fail, the buffers will be allocated
> > exactly as they'd be if GPU_READ_CPU_READ_WRITE were used instead.
> > 
> > Bug: b/71837407
> > Change-Id: I3a03daf721f1cc04038a4f6f91985b5affe2a276
> > Reviewed-on: https://chromium-review.googlesource.com/884401
> > Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
> > Reviewed-by: Miguel Casas <mcasas@chromium.org>
> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#532286}
> 
> TBR=dalecurtis@chromium.org,mcasas@chromium.org,dcastagna@chromium.org,hoegsberg@chromium.org,ddavenport@chromium.org
> 
> Change-Id: I13c479543ac53694f6f413c83aa15481e9c80c53
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: b/71837407
> Reviewed-on: https://chromium-review.googlesource.com/890978
> Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
> Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532344}

TBR=dalecurtis@chromium.org,mcasas@chromium.org,dcastagna@chromium.org,shimazu@chromium.org,hoegsberg@chromium.org,ddavenport@chromium.org

Change-Id: I92a0379b36cdc6b21bf609ab69a467acbad23c9e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b/71837407
Reviewed-on: https://chromium-review.googlesource.com/891718Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532513}

Consolidate expectations for the imported Web Platform Tests for
legacy multibyte encodings (Chinese, Japanese, Korean) which exercise
tens of thousands of code points and often time out (>30s) even when
marked as slow.

TBR=kbr@chromium.org

Bug: 805725,736056,749070
Change-Id: I12051e3c3a20730783aabb39376b55e9788450f4
Reviewed-on: https://chromium-review.googlesource.com/889538Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532512}

Updating from 65.0.3322.0_rc-r1.

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

TBR=agrieve@chromium.org, gbiv@chromium.org

Bug: None
Test: CQ
Change-Id: I36614584245a42f039cf40690a3b9172b2c572c7
Reviewed-on: https://chromium-review.googlesource.com/891618Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532511}

This CL adds an extra StateChangeDetail parameter to the
Observer::OnSecureChannelStatusChanged() function. This parameter is
currently unused, but it will be used by a future CL to better handle
connection retries.

Bug: 805218, 672263
Change-Id: I4dc80f324d74a6df54113b058dec0bb07459ae3f
Reviewed-on: https://chromium-review.googlesource.com/888038Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532510}

This CL brings the following changes to promptly freeing and coalescing:
1) Promptly freed objects on already swept pages are immediately added to the free list.
2) For promptly freed objects on not already swept pages we only clear the mark bit.
3) The promptly_freed_size_ counter is explicitly set to 0 before sweeping because sweeping will take care of coalescing as well.
4) The dead bit is removed.
Note that coalescing before sweeping completed can not happen.

Future outlook: As a next step we will evaluate if we need coalescing and if we need it we have to make it jank friendly.

Bug: chromium:804279, chromium:633030
Change-Id: I35dfae80ae0e7ed6cfbc91877d97d0b5fc26498e
Reviewed-on: https://chromium-review.googlesource.com/873974
Commit-Queue: Hannes Payer <hpayer@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532509}

Changing the default mode to AllAccess from BlacklistOnly.
Changing the default so that we can show printers if the
NativePrintersAccessMode policy is unset.

Changes to policy_templates.json will be separate.

Bug: 805825
Change-Id: I62ef189749ad2209ba715835e4a1ffda8150573e
Reviewed-on: https://chromium-review.googlesource.com/887366Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532508}

+ Speculative fix for ModalDialogManagerTest#testShow_UrlBarFocused:
  Wait for url bar focused callback to make sure dialogs are updated.
+ JavascriptTabModalDialogTest#testAlertModalDialogMessageFocus:
  Use landscape mode for test to make sure alert message is long enough.

Bug: 802254, 800377
Change-Id: Ic7549b81aa1ca8900858260f6311772014c7de37
Reviewed-on: https://chromium-review.googlesource.com/887823Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532507}

Bug: 793985
Change-Id: I840f950d7de6e6ac8506ed8937bbe9a3e270d5da
Reviewed-on: https://chromium-review.googlesource.com/887820Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532506}

Background:
Upon suspend, DisplayManager::SetSoftwareMirroring(true) will be called to
clear current mirroring source and destination displays. But mirror mode
is not enabled because DisplayManager::OnNativeDisplaysChanged() will
receive empty display info and stop before reconfiguration. Later upon
resume, mirror mode will not be restored because the mirror info is cleared.

Changes:
Prevent DisplayManager::SetSoftwareMirroring(true) from clearing the
mirroring source and destination displays as they will be cleared later
in DisplayManager::OnNativeDisplaysChanged().

Bug: 797016
Change-Id: I3b987e5bc13a72313f5273262e96ed26b7ca347c
Reviewed-on: https://chromium-review.googlesource.com/857548
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532505}

The "accessibility_autoclick" service is a small mojo app that
implements the "automatically click when the mouse stops moving"
feature for users with difficulty clicking the mouse. It was
missing from ash's manifest file.

This fixes browser_tests AccessibilityFeatureaApiTest and
ChromeOSInfoPrivateTest.TestGetAndSet under mash.

Bug: 678687, 805713
Test: browser_tests --mash
Change-Id: I3611b80209809247a64987d339cc513e1caeee06
Reviewed-on: https://chromium-review.googlesource.com/889524
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532504}

`new` never returns nullptr per standard (in Chromium, we crash the process
on out-of-memory instead).

Also, in the first case, the image in the ImageBitmap is checked for nullness
right above, so that check isn't needed either.

Bug: 805881
Change-Id: Ieff5bdf15813bfb0f3087ec925f74ecacc77df7c
Reviewed-on: https://chromium-review.googlesource.com/887758Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532503}

The current implementation of UpdateService doesn't take into consideration
the installation of delayed extensions. This will fix that.

Also add flag/feature to prepare running the new update service as an
experiment in Finch.

Change-Id: If858e74ac2276829de2d2e9b3babc9c7182e49d9
Reviewed-on: https://chromium-review.googlesource.com/872119
Commit-Queue: Minh Nguyen <mxnguyen@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532502}

See https://bugs.chromium.org/p/chromium/issues/detail?id=671732#c11

This CL was uploaded by git cl split.

R=dcheng@chromium.org

Bug: 177475,671732
Change-Id: I7b147b9bf9b5ed7853a9a98132812a3557972326
Reviewed-on: https://chromium-review.googlesource.com/890432Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532501}

* Separates the title from the promotion content (adds a secondary-style
  Label for body content).
* Removes the "no thanks" button (still present in the Cocoa version).

Bug: chromium:654115, chromium:654117
Change-Id: I83274934bfff8eaec6e5065233661ddd91447d39
Reviewed-on: https://chromium-review.googlesource.com/887726Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532500}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/23c165f3c831..7a4ced2773b2

$ git log 23c165f3c..7a4ced277 --date=short --no-merges --format='%ad %ae %s'
2018-01-26 ehmaldonado Report progress of gclient sync during fetch.

Created with:
  roll-dep src/third_party/depot_tools


The AutoRoll server is located here: https://depot-tools-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=phajdan.jr@chromium.org

Change-Id: Id0d796613dfb0d102156afbea486aadfa2299482
Reviewed-on: https://chromium-review.googlesource.com/891301
Commit-Queue: depot-tools-roller . <depot-tools-roller@chromium.org>
Reviewed-by: depot-tools-roller . <depot-tools-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532499}

https://pdfium.googlesource.com/pdfium.git/+log/dbac8ca4f5d7..bc4869293d78

$ git log dbac8ca4f..bc4869293 --date=short --no-merges --format='%ad %ae %s'
2018-01-29 thestig Fix identical if/else blocks.
2018-01-29 thestig Remove duplicate assignments in sycc420_to_rgb().
2018-01-29 thestig Roll V8 to ee5d9a0c.

Created with:
  roll-dep src/third_party/pdfium
BUG=805881,805881


The AutoRoll server is located here: https://pdfium-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=dsinclair@chromium.org

Change-Id: Id658b85157c1332418f1509c8653ecab8390cfae
Reviewed-on: https://chromium-review.googlesource.com/890631
Commit-Queue: <pdfium-deps-roller@chromium.org>
Reviewed-by: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532498}

As requested by the test team, this will eliminate a manual test case.

BUG=806279
R=ymalik

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I5e08e7b8e30e65cebf680d3449d15a0b293de7b1
Reviewed-on: https://chromium-review.googlesource.com/890392Reviewed-by: Yash Malik <ymalik@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532497}

unsized-media sets a default size for laying out intrinsically sized
images / videos.
The feature is allowed for all origins by default.
When disabled, any intrinsically sized images / videos will be using
the default dimension (300 x 150) to prevent relayout.

Bug: 623682
Change-Id: I1bd105ded2580349e2a2b177e87b70417403cb59
Reviewed-on: https://chromium-review.googlesource.com/865159Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532496}

In the OOPIF-based guest implementation of attachment, the contentWindow
of the internal iframe element is used to identify the local frame to
swap for a remote frame. When the guest is destroyed, we currently don't
"reset" the internal iframe element so that it can be used for another
attachment. When we try to attach, the frame is still remote, which
causes GuestViewInternalCustomBindings::AttachIframeGuest to be unable
to find the frame to swap.

We now replace our internal iframe element upon guest destruction, so
that the frame is local when we reattach.

Bug: 800407
Change-Id: I4424793c7c0230d62a424765bc3c288080b2e0b9
Reviewed-on: https://chromium-review.googlesource.com/871292Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532495}

Bug: 801783

Change-Id: I78455d0a50869e7a81b9bfe8613e53bcb5973c80
Reviewed-on: https://chromium-review.googlesource.com/884441Reviewed-by: Robert Phillips <robertphillips@google.com>
Commit-Queue: Brian Salomon <bsalomon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532494}

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I7cdba1e84b853eeaff281093555e8757dc1616ed
Reviewed-on: https://chromium-review.googlesource.com/882396Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532493}

But drop them when they become available if we're in the SUSPENDED
memory state.

Deleting busy resorces doesn't actually free any memory, it just moves
the ownership solely into the ResourceProvider until they become
available. Instead, we can keep them in the busy list, and when
they are available, decide to keep them or not based on the
memory state instead.

This should also improve things by reducing memory footprint in the
SUSPENDED memory state if OnPurgeMemory() isn't being called but
new tile resources are being made and released.

R=ericrk@chromium.org, vmpstr@chromium.org

Bug: 730660
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I24e1a6f38c88fa278566849174a315bff71ed375
Reviewed-on: https://chromium-review.googlesource.com/886862
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532492}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/c1717655..787ecbb3

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;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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I29e1ddf6f049f287169f92091db9ec3c3df9c503
Reviewed-on: https://chromium-review.googlesource.com/889869Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532491}