GitLab

https://chromium.googlesource.com/media_router.git/+log/6fc8d5201d09..8c27673ed823

$ git log 6fc8d5201..8c27673ed --date=short --no-merges --format='%ad %ae %s'
2018-02-16 mfoltz Remove Mojo error logging in MediaRouteController
2018-02-15 mfoltz Updates the Cast MRP for correct mirroring route descriptions [#2]
2018-02-15 mfoltz [DIAL] Removes in-extension DIAL discovery.
2018-02-02 mfoltz [Dial MRP] Added a config to enable/disable extension side DIAL sink query
2018-02-01 mfoltz [LSC] Replace uses of @code within .js files with Markdown backticks.
2018-02-01 mfoltz [MRP] Use device id as sink id in MRPs
2018-01-31 mfoltz [MR] log last 4 characters of a sink ID
2018-01-30 mfoltz [DIAL MRP] DIAL provider should not return Chromecast Ultra devices for sink queries
2018-01-24 mfoltz Renamed all Weave-specific code to include the word "Weave".
2018-01-11 mfoltz Adds a mirror activity object.
2018-01-02 mfoltz Runs genjsdeps over the Media Router Extension code base.
2017-11-29 mfoltz MediaRemoter: Add handling of media remoting pref value changes.
2017-11-27 mfoltz [Cast Streaming] Add support for media remoting controls from MR dialog.

Created with:
  roll-dep src/chrome/browser/resources/media_router/extension/src

Change-Id: I6acdfe820b7e1efd4d0538e96822c470d2f6f7ce

TBR=amp

Change-Id: I6acdfe820b7e1efd4d0538e96822c470d2f6f7ce
Reviewed-on: https://chromium-review.googlesource.com/924613
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537890}

This reverts commit 6c5d6c38.

Reason for revert: Must be rolled back in tandem with https://chrome-internal-review.googlesource.com/c/chrome/ios_internal/+/573755 

Original change's description:
> Relands 697d4f8f after fixing upstream change.
> 
> Bug: 808113
> 
> Original change's description:
> >Enables Mailto Handling with Google UI by default.
> >
> >Bug: 808113
> >Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
> >Change-Id: I2b475e6fd474c900ed1984010d15a3e1e31c2af0
> >Reviewed-on: https://chromium-review.googlesource.com/922930
> >Commit-Queue: Daniel Blakemore <danblakemore@google.com>
> >Reviewed-by: Peter Lee <pkl@chromium.org>
> >Cr-Commit-Position: refs/heads/master@{#537373}
> 
> Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
> Change-Id: I3c9821bd95d1ac74fcc4dc4b7c4474ce0b40c5da
> Reviewed-on: https://chromium-review.googlesource.com/924635
> Reviewed-by: Peter Lee <pkl@chromium.org>
> Commit-Queue: Daniel Blakemore <danblakemore@google.com>
> Cr-Commit-Position: refs/heads/master@{#537870}

TBR=pkl@chromium.org,danblakemore@google.com

Change-Id: I4f5da1bfc9fbaea35999891528d5086fb0bc9605
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 808113
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Reviewed-on: https://chromium-review.googlesource.com/927501Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537889}

In preparation to update WebView on ChromeDriver Android test bot to
current stable version, adjust the test filter for webview shell, so
that it is based on the filter for Chrome stable.

Change-Id: Ib2143dd6fa46cbda050a53dadfdcbbc7c9eb46f5
Reviewed-on: https://chromium-review.googlesource.com/917161Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537888}

Bug: angleproject:2362
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: I0cc7aa1b2a0e00009f1184bb1c97e40d809cf032
Reviewed-on: https://chromium-review.googlesource.com/927201Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Luc Ferron <lucferron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537887}

ChromeDownloadDirTest.testDownloadDirectoryOverridesExistingPreferences
was flaky due to race condition in deleting temporary directories.
Add retries, and ignore the error if temporary directories can't be
deleted after retries. This is similar to what we do in ChromeDriver
itself (see chromedriver/chrome/scoped_temp_dir_with_retry.cc).

Bug: chromedriver:992
Change-Id: I8421b311566dc1e5bef42658ff772dde1a683d30
Reviewed-on: https://chromium-review.googlesource.com/918065Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537886}

https://chromium.googlesource.com/angle/angle.git/+log/029e8ca77884..e703c606f397

$ git log 029e8ca77..e703c606f --date=short --no-merges --format='%ad %ae %s'
2018-02-20 jmadill Add gl::RenderbufferState shared state helper.
2018-02-02 geofflang D3D11: Downsample when copying to emulated 16-bit texture formats.
2018-02-20 jmadill Add empty file to prevent git clean from deleting the tools folder.
2018-02-14 geofflang StateManagerGL: Use dirty bits for VAO bindings.
2018-02-16 cwallez Expand the EGLIOSurfaceClientBufferTests

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

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

This change adds a new GL command (intended for use via the
RasterInterface) which copies data from a normal-bit-depth (8888)
texture to a low-bit-depth (4444) texture, performing an unpremultiply
and a dither in the process.

This is a pretty special-case extension designed to address the
speicific issues that:
- GPU raster output is currently not dithered, leading to banding in
   some cases
- Dithering premultiplied output does not alleviate all banding.
- Storing premultiplied ouptut in 4444 textures can lead to artifacts
   even if dithered.

This extension will be used when Chrome rasterizes to 4444 textures on
low-end devices.

To achieve this behavior, we add a "dither" parameter to the
CopyTextureCHROMIUMResourceManager, allowing it to perform a dither
while copying. The new extension leverages this existing class.

The actual dither code is the same logic used internally in Skia, and
has been tested there for performance. The only difference is that in
our case we dither alpha as well.

Bug: 789153
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: Ibce954f90eb7c461e127c5eb8bcf3ad9799bfe20
Reviewed-on: https://chromium-review.googlesource.com/899664
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537884}

The ResourcePool used to be created for OneCopy mode with a kDefault
ResourceTextureHint, rather than kFramebuffer. This was a copy-paste
from GpuRasterBufferProvider, which does want to use textures for
framebuffer attachment.

R=vmpstr@chromium.org

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

For historical reasons, we modified the ARC framework to let each app
to report the cursor position relative to its window.

Now, the modification can be removed because we phased out Android-M based ARC.
More importantly, the modification *should* be removed, because it is not
compatible with third-party Android IMEs, and it caused a minor misplacement
in corner cases.

Note that we still need to keep the old window-relative mode, since ARC
notifications are still thinking themselves to be placed at (0,0), and thus
relying on this mode.

BUG=b/73097347
TEST=components_unittests ArcImeServiceTest
TEST=Manually on PlayStore, Settings, Hangouts (notifications),
  Dialog in Gallery KK" app, with and without multi-displays.

Change-Id: I8cd4581f4ccb5fb331c5686510b225527fea69f5
Reviewed-on: https://chromium-review.googlesource.com/902987Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Kazuhiro Inaba <kinaba@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537882}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/3ade6e121416..7707c8a10d46

$ git log 3ade6e121..7707c8a10 --date=short --no-merges --format='%ad %ae %s'

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

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

This reverts commit 250fb9b3.

Reason for revert: The bug which caused the failure has been fixed.

Original change's description:
> Disable failing blink_perf.canvas story on 5, 5X, and 5X webview
> 
> TBR=ashleymarie@chromium.org
> NOTRY=true
> 
> Bug: 812615
> Change-Id: Ib89c68b30e3b0f33eded7e35572dd71208d60a4d
> Reviewed-on: https://chromium-review.googlesource.com/922788
> Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
> Reviewed-by: Charlie Andrews <charliea@chromium.org>
> Commit-Queue: Charlie Andrews <charliea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#537309}

TBR=charliea@chromium.org,ashleymarie@chromium.org

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

Bug: 812615
Change-Id: I2cb330d935fdf42d41c00e05637e3dee9e22989f
Reviewed-on: https://chromium-review.googlesource.com/927202Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537880}

The SpellCheckHost mojom has some platform-dependent APIs.

This patch uses the EnableIf mojo attribute so that we don't need
to leave dummy API implementations on unsupported platforms.

Bug: 813217
Change-Id: I407ebc6687c404b1583ceeac346a29cb775847ee
Reviewed-on: https://chromium-review.googlesource.com/905579
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537879}

Support library update regressed start up time by 10 ms
(crbug.com/782956). Webview uses support library through an indirect
dependency chain, such as DropdownAdapter, AutofillKeyboardAccessory,
and GMS core library.

This can be explained by what we do in ResourceRewriter.
ResourceRewriter checks for dependency graphs and call
onResourcesLoaded() for all the reachable R's. This is a necessary
step to avoid conflicts between library apks and main apk, and webview
is doing this on its own.

However, resource rewriting takes quite some time, as it creates
dependency graphs all the way into support library and GMS core
library. Local experiment shows that setting up resources on a separate
thread can reduce start up time by 15-50 ms.

AwBrowserProcess requires AwResource#getConfigKeySystemUuidMapping()
so there is a chance that it can crash if startUpResources() is not
finished. When tested, calling startUpResources immediately before
AwBrowserProcess seems to work.

Bug: b/69005401, 782956
Change-Id: Ie05ffd68063013a251bb5af3618bb78b2576dcbe
Reviewed-on: https://chromium-review.googlesource.com/923174Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537878}

The tab recording alert indicator icon no longer has a default color
assigned to it in the icon file. Even when touch optimized mode is
disabled, the correct color needs to be retrieved from the theme
provider.

Bug: 813763
Change-Id: I6cf37194aa1498520d973ee4300499ed402b10dc
Component: Tab alert icon, recording icon, color
Reviewed-on: https://chromium-review.googlesource.com/927110Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537877}

The paint recording scale factor is set to 1 when pixel canvas is
disabled. We cannot use the value of PaintContext::device_scale_factor
for the recording scale factor in such cases.

Bug: 813463
Change-Id: If51bfde2e271ce863cf3971016ee6347cbce592a
Component: Tabs, Clipping, Scaling
Reviewed-on: https://chromium-review.googlesource.com/927182Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537876}

Problem:

Sometimes, one section of a form appears in multiple groups over
time. This causes field by field situation from second group onward,
because we group them all as one section, and would consider the
fields which appear later as already filled. This is also an
inconsistency, because the browser side fills them, but the
renderer side doesn't.

Examples:

oup.com
tradepub.com

Solution:

Don't fill hidden fields on the browser side. This way, they
can get filled in later steps for real. This is also more
consistent with a real user's action.

As a result of this change, we can no more say if a section is
autofilled as a unit. Some fields may be autofilled and some may not.
We should consider the fields separately. So, we should take care of:

1.filling/previewing the form.

2.deciding if a credit card number will be filled.

Tests added and modified.

Note: Previously we would fill the hidden fields (on browser side),
because we were not looking at the most updated version of the form,
and couldn't trust the given visibility status of a field. This is
not the case anymore. This change is based on the new version.

Bug: 807780

Change-Id: I297ef33ce5952bab8ff5fce90bf4fc4d6a09731e
Reviewed-on: https://chromium-review.googlesource.com/919525
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537875}

This format isn't part of the TransferableResource::MakeFoo() helpers
but is important nonetheless for memory accounting, and would be
important for software resources. For GL the format is known in the
service so it ends up not being used for correctness.

R=ericrk@chromium.org

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

Bug: internal b/71879643

Test: Build cast_shell
Change-Id: I47b8ab347a9f307e8c504dc609ab1eebd4a6cc52
Reviewed-on: https://chromium-review.googlesource.com/924279Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Jiawei Li <lijiawei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537873}

https://webrtc.googlesource.com/src.git/+log/6bd3cddcef0c..1896cece014c

$ git log 6bd3cddce..1896cece0 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-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.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Bug: NONE
Change-Id: Ie55f6bdde715bba84dfaba5eb51acbd559e28ed9
Reviewed-on: https://chromium-review.googlesource.com/926712Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Commit-Queue: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537871}

Bug: 808113

Original change's description:
>Enables Mailto Handling with Google UI by default.
>
>Bug: 808113
>Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
>Change-Id: I2b475e6fd474c900ed1984010d15a3e1e31c2af0
>Reviewed-on: https://chromium-review.googlesource.com/922930
>Commit-Queue: Daniel Blakemore <danblakemore@google.com>
>Reviewed-by: Peter Lee <pkl@chromium.org>
>Cr-Commit-Position: refs/heads/master@{#537373}

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I3c9821bd95d1ac74fcc4dc4b7c4474ce0b40c5da
Reviewed-on: https://chromium-review.googlesource.com/924635Reviewed-by: Peter Lee <pkl@chromium.org>
Commit-Queue: Daniel Blakemore <danblakemore@google.com>
Cr-Commit-Position: refs/heads/master@{#537870}

BUG=789768
R=dpranke

Change-Id: I4c31c8c2c2fefad5337dff51727cbfd9c58a89b4
Reviewed-on: https://chromium-review.googlesource.com/924391Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537869}

- Removes ReserveMemory method.
- Removes ReleaseReservedMemory, this is now just base::FreePages.
- Removes SetProtection, this is now base::SetPermissions.
- Removes dependency on sandbox/linux. base::AllocPages / FreePages
  now updates address space limits.

Bug: chromium:799573
Change-Id: Iabc57c61511dfdc7b7ca2aa93c56ed21a22692f4
Reviewed-on: https://chromium-review.googlesource.com/923173Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537868}

Bug: 758632
Change-Id: I2aa7e817265a5d7bd25823aa47544f53ccc976c1
Reviewed-on: https://chromium-review.googlesource.com/926567Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Ashley Enstad <ashleymarie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537867}

https://skia.googlesource.com/skia.git/+log/c68ba1d7d981..300cc5b5c1e1

$ git log c68ba1d7d..300cc5b5c --date=short --no-merges --format='%ad %ae %s'
2018-02-20 caryclark fix IRect doc
2018-02-20 halcanary SkQP: update README.md
2018-02-20 fmalita Add SkRect::contains(SkScalar x, SkScalar y)
2018-02-20 csmartdalton Drop unused support for MSAA sample locations
2018-02-20 halcanary android_build_app: optionally disable gradle daemon
2018-02-20 fmalita [sksg] Add 'plane' geometry node
2018-02-20 stephana Add SKQP bot to build universal APK to master
2018-02-15 csmartdalton ccpr: Fix a couple issues with tessellation and winding
2018-02-20 jvanverth Some more cleanup of GrDrawOpAtlas compaction
2018-01-25 mtklein Reland "remove third_party/etc1"
2018-02-20 halcanary Docs: clean up links
2018-02-14 csmartdalton Drop unused shader support for multisample interpolation

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

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

Use the procedural controller instead of the GLTF controller. Also
remove the GLTF resource and the related parser since they are now
unused. The GLTF parser can be re-submitted later when we have a use
for it.

Also reduce the number of polys of the procedural controller to avoid a
perf regression.

Bug: 799606, 779108, 770891
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:closure_compilation;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: I93209628fbcf20cf708b47c78689a951851f9b4b
Reviewed-on: https://chromium-review.googlesource.com/922161Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537865}

Without the --system-clang flag, ycmd fails to find the system headers,
which severely limits its usefulness. The flag is documented as
unsupported, but it's recommended by the maintainers on OSX:
https://github.com/Valloric/YouCompleteMe/issues/2536#issuecomment-333909807

Change-Id: I93aeb12656d32e0fa2099aa0c703fcb6f7154bfb
Reviewed-on: https://chromium-review.googlesource.com/925102Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Jianpeng Chao <chaopeng@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537864}

The error appears when we try to update the dialog height before the
container element is initialized. We will update later when the element
is initialized.

Bug: 799912
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ia24832275a46e753da48be9223f0a3ec83463d04
Reviewed-on: https://chromium-review.googlesource.com/919310Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537863}

This flag delays execution of base::TaskPriority::BACKGROUND tasks
until shutdown.

Bug: 726937
Change-Id: I2ce529a410382e7199558a0ed95476767b14786b
Reviewed-on: https://chromium-review.googlesource.com/919866
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537862}

The code in its current form gives the impression that there's a
dependency on the initial value of the 'fill' property, while all we
really want to say here is 'black'. Use a more direct approach.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ib75ba965c585771e9a009f91f0055a592a37c1b0
Reviewed-on: https://chromium-review.googlesource.com/926845Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#537861}

Use base::FeatureList and about:flags to enable V2 feature.
Default for this flag is DISABLED.

Bug: 657076
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I4b5ee8c95a79f533fded6b717efa0dd6c0bae895
Reviewed-on: https://chromium-review.googlesource.com/900543Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537860}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

Change-Id: I117ee483681a2788f93f544dee037dee856f7680
Reviewed-on: https://chromium-review.googlesource.com/926566Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537859}

When paused on an error, the debugger paused message is not showing
the correct red styles.

Screenshot: https://imgur.com/a/R9tv6

Bug: 812713
Change-Id: I23a95848b7727a2357614172c93b055fa5c185b8
Reviewed-on: https://chromium-review.googlesource.com/922396
Commit-Queue: Erik Luo <luoe@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537858}

Since the clear button is in omnibox, it makes sense for it to be
directly configured in the omnibox layer, without going to the location
bar.

Bug: None
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I51be645345550517e120939416a7e0664b74cf87
Reviewed-on: https://chromium-review.googlesource.com/924424
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537857}

- AudioParam IDL test:
  Actually add the IDL to the test.  Also removed unused helpers.js.
- MediaElementAudioSourceNode
  Fix error because the expected result is mono, so only has one channel.
  However, this still fails on bots because there's no audio hardware to
  drive the online context.

Bug: 626703
Test: the-audioparam-interface/idl-test.html
Change-Id: I987ad1219da1b6b6ef677f2923416634fa281d5f
Reviewed-on: https://chromium-review.googlesource.com/920261
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537856}

This CL tentatively fixes GLImageIOSurface/GLImageBindTest/4
on Nvidia + 10.13.4 Mac OS X systems; the error log points
to the current workaround swizzling the R and B channels
specifically on such system and OS version combination doing
the wrong thing, so let's removes it and see if it does the
trick.

Bug: 813846
Change-Id: I013da016158860da05b1b2bf0c363d29afdbef2f
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
Reviewed-on: https://chromium-review.googlesource.com/926763Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537855}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

Change-Id: I89b52d89edbaff91c681700fa58bd591757abc28
Reviewed-on: https://chromium-review.googlesource.com/923346Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537854}

Currently demuxer stream limits are 12MiB for audio and 150MiB for video,
regardless of the platform. This means that when playing long videos Chrome
will slowly allocate up to 162MiB. Most low-end Android devices can't afford
allocating that much, which translates to bad user experience: first device
becomes sluggish, as OS tries hard to kill other processes / move memory to
zram. Eventually (since renderer keeps allocating) Android gives up and kills
Chrome.

Turns out that Chromecast had similar issues and ended up lowering demuxer
limits to 2MiB for audio / 30MiB for video.

This CL turns demuxer limit constants into functions and selects lower
values on low-end Android devices.

Bug: 810906
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: I33fcd7d4916379abcb1f56cf9289928dfe3788a7
Reviewed-on: https://chromium-review.googlesource.com/922884Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Dmitry Skiba <dskiba@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537853}

Move the credit card autofill touch bar logic from
AutofillPopupViewCocoa to AutofillPopupControllerImplMac
so that is can be used on both Toolkit and Cocoa
autofill popups.

Bug: 812658
Change-Id: Ic8d788dddabb909edee46da46899d759447a7c7d
Reviewed-on: https://chromium-review.googlesource.com/915438Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Sarah Chan <spqchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537852}

This CL implements the touch-optimized design of the New Tab
Button in both incognito and normal modes. Button is flat
with no highlight, and has an ink drop ripple effect.

Demo is posted on the bug.

BUG=805245
TEST=manually

Change-Id: I33a2e5e213193318b70e1c01ee330a67d6af21f0
Reviewed-on: https://chromium-review.googlesource.com/903375
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537851}