GitLab

We want Chromium to build with enable_webrtc=false. I will initially
add a build bot in chromium.webrtc.

Bug: chromium:811678
Change-Id: If3f23a70f0102f5b65bb46e5e91eee3c0b1bbeb2
Reviewed-on: https://chromium-review.googlesource.com/960125
Commit-Queue: Patrik Höglund <phoglund@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544013}

This flag was originally added to ui::base::win to suppress a specific
error message when attempting to open a file via the shell using the
"open" verb. The flag has additional side-effects and shouldn't be used
when invoking ShellExecute().

R=grt@chromium.org

Bug: 819809
Change-Id: I7db2344982dd206c85a73928e906c21e06a47a9e
Reviewed-on: https://chromium-review.googlesource.com/966964
Commit-Queue: Greg Thompson <grt@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544012}

This reverts commit 1fa1c441.

Reason for revert: broke downstream builders

Original change's description:
> android build: Split process_resources GN rule and script.
> 
> The process_resources() GN template and the associated
> process_resources.py script are huge and difficult to understand
> because they can be used to perform two slightly related
> different things.
> 
> In preparation for a future CL that will introduce a new resource
> compilation mode, this CL tries to clarify the situation by splitting
> them into two sets of GN template + script:
> 
>    - prepare_resources() + prepare_resources.py, which are
>      used to create .resources.zip archives of raw/uncompiled
>      resources for resource related targets, as well as
>      generating a corresponding R.txt and .srcjar(R.java)
>      file.
> 
>      This corresponds to what process_resources() did when
>      it was called from android_resources() and junit_binary().
> 
>      Note that this always generates non-final resource IDs,
>      as well as a dummy onResourcesLoaded() method, necessary
>      to compile, but not link, the ResourceRewriter class
>      used to implement the system webview feature.
> 
>    - compile_resources() + compile_resources.py, which are used
>      to compile all resource dependencies of a given binary
>      (e.g. android_apk) into an intermediate .ap_ file.
> 
>      This corresponds to the behaviour of process_resources()
>      when called from android_apk(). This generates final
>      resource IDs by default, unless |shared_resources| or
>      |shared_resources_whitelist| is used.
> 
>      Also, as a simplification, |shared_resources_whitelist|
>      now implies |shared_resources|, except that it restrict
>      the list of non-final resource IDs.
> 
> - Removed generate_constant_ids, since compile_resources()
>   will always generate constant ids unless shared resources
>   are being used. And prepare_resources() always generates
>   non-constant IDs, as before the CL.
> 
> + Add documentation for the prepare_resources() and
>   compile_resources() internal GN rules, to make them
>   a little less intimidating.
> 
> + Removed |app_as_shared_lib|, since even before this CL all
>   resources were generated with package ID 0x7f anyway, or
>   fixed a compile_resources() time. Hence |shared_resources|
>   did the exact same thing.
> 
> + Improve --help output for prepare_resources.py and
>   compile_resources.py by using option groups for inputs
>   and outputs.
> 
> R=​agrieve@chromium.org,yfriedman@chromium.org,estevenson@chromium.org,trevordixon@chromium.org
> 
> Bug: 820459
> Change-Id: If05ac24a57c4dfa11f9ce43c30ab22e957b2765d
> Reviewed-on: https://chromium-review.googlesource.com/957095
> Commit-Queue: David Turner <digit@chromium.org>
> Reviewed-by: agrieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543957}

TBR=digit@chromium.org,yfriedman@chromium.org,agrieve@chromium.org,estevenson@chromium.org,trevordixon@chromium.org

Change-Id: I38d7922928cc6222750e057bc4a602a1faaec59e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 820459
Reviewed-on: https://chromium-review.googlesource.com/968461Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544011}

This patch makes SignedExchangeHandler populate the minimal set of
timing info for the HTTP exchange response, so that devtools' network
timeline will show reasonable values.

Bug: 803774
Change-Id: Ida0d34f7bab86f5ff674b776fe5fca511111c87c
Reviewed-on: https://chromium-review.googlesource.com/967632Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544010}

Change-Id: I2e894379abc801ef364a9228b89e3cc23eaf408c
Reviewed-on: https://chromium-review.googlesource.com/968247
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544009}

last_auth_error_ was set from OnGetTokenFailure, but then never cleared
in onGetTokenSuccess. This meant that the error could stay around, even
if the causing token issue was resolved.

BUG=822182

Change-Id: I135baa55d8e81860313dd02f2ca432f0482c3c10
Reviewed-on: https://chromium-review.googlesource.com/964334
Commit-Queue: Florian Uunk <feuunk@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544008}

As skia font cache, we need to limit the memory usage of skia resource cache
for the low-end device as well. But, as the font cache, it's hard to estimate
what is the limit value the best for each low-end device. So it would be good
if we give them the power to limit to use the resource cache. This CL introduces
a new command line switch to limit the skia resource cache size.

Bug: 823210
Change-Id: Icc55a8701fe2fa94bdc0ee09b428c19031c131a5
Reviewed-on: https://chromium-review.googlesource.com/968006
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544007}

https://webrtc.googlesource.com/src.git/+log/8a1b20a21329..9fa35e528528

$ git log 8a1b20a21..9fa35e528 --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: Id4c6302826bb881e8b31332c5304b354457130c5
Reviewed-on: https://chromium-review.googlesource.com/967951
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#544006}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6887bb98..8c5929de

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;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: Id1149be5925c8733c6cf4be6ad75bee0ca955827
Reviewed-on: https://chromium-review.googlesource.com/967953Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544005}

By explicitly closing the keyboard before closing the search, the
keyboard will no longer overlay the visible elements in tests.
The slowly disappearing keyboard hid elements from espresso and failed
some test runs on small screen devices.

Change-Id: I45e6548395a3875e79d9cad6a7655e6d67163d2a
Reviewed-on: https://chromium-review.googlesource.com/966034
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544004}

The former is a deprecated alias.

Bug: None
Change-Id: Ib4c1132135de159a932ebc26454f5df15274e25d
Reviewed-on: https://chromium-review.googlesource.com/966602
Commit-Queue: Niels Möller <nisse@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544003}

This CL implements WorkerModuleFetchCoordinator that actually initiates module
loading on the main thread in response to requests from
WorkerOrWorkletModuleFetcher on the worker thread.

Design doc:
https://docs.google.com/document/d/1IMGWAK7Wq37mLehwkbysNRBBnhQBo3z2MbYyMkViEnY/edit#heading=h.637avx8i5qtn

Bug: 680046
Change-Id: Ib845662436356b2966ed987a88be33ed5dc970f8
Reviewed-on: https://chromium-review.googlesource.com/963874
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544002}

Using wpt-import in Chromium 7b38a1f6.

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

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

TBR=qyearsley

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

It seems odd that he's not already in the the OWNERS and is effectively
owner for the virtual/fake stuff already.

Change-Id: I7ad37eb9406539df6a666c4e299d684405c2c3cb
Reviewed-on: https://chromium-review.googlesource.com/967064
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544000}

This CL introduces Editor::Command::CanExecute(), and move the predicate
in Editor::Command::Execute() to it, make Editor::Command::Execute()
simple and improve code health.
Signed-off-by: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Change-Id: Iae25f9ebd4d7554e83a9a819c562fae85c2dedc6
Reviewed-on: https://chromium-review.googlesource.com/954773Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543999}

This CL change Editor::CreateCommand to be const type for
improving code health.
Signed-off-by: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Change-Id: I1e17c38f346d07f06cae0e736da0d550eacf3f74
Reviewed-on: https://chromium-review.googlesource.com/965723Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543998}

Right after the target Element gets detached from the document tree,
the last size change event is dispatched to ResizeObserver.  At this
moment, the target Element is already detached from the document and
we cannot rely on the wrapper-tracing path of:
    Document --> Element --> ElementRareData --> ResizeObserver
So, we need another path to perform the wrapper-tracing for
ResizeObserver.

This patch makes ResizeObserver ActiveScriptWrappable, so that the
following path of wrapper-tracing will be available:
    V8 wrapper of ResizeObserver --> blink::ResizeObserver

I confirmed that this patch fixes the crash issue at a certain
website.

FYI: You find some discussion at https://crrev.com/c/960482 .

Bug: 815058
Change-Id: I43c4695304f7f54b819f0c2dfbc4a5a8cf9df8f7
Reviewed-on: https://chromium-review.googlesource.com/964075Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543997}

This is a preparation CL for module scripts on workers.

Before this CL, postMessage() requests during dedicated worker startup are
queued until a worker thread is created and a thread initialization task is
posted to the worker thread. This works for classic scripts because classic
script evaluation happens synchronously after thread initialization and there is
no timing to interleave the message tasks. However, this is not applicable for
module scripts because module script evaluation happens asynchronously on the
worker thread. This allows posted tasks run before script evaluation and results
in dropouts of the Message events.

This CL makes sure to post message tasks after script evaluation. ObjectProxy on
the worker thread notifies MessagingProxy on the main thread of the completion
of script evaluation, and then MessagingProxy posts queued messages.

Bug: 680046
Change-Id: I7cb32cc8911a7bbe9e5d83e5f7fceb333bb3125a
Reviewed-on: https://chromium-review.googlesource.com/967914
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543996}

Generic, platform-independent decoders - {H264,VP8,VP9}Decoder - operate on
generic Picture classes - {H264,VP8,VP9}Picture - and use them to communicate
with platform-specific Accelerators.

Accelerators augment these Picture classes with platform-specific metadata
in order to process them. This includes platform-specific representations
of buffers used as targets for decoding a given picture, such as VASurface
for VaapiVDA.

This platform-specific metadata is encapsulated in Accelerator-specific
{Vaapi,V4L2}DecodeSurface classes.

To tie {Vaapi,V4L2}DecodeSurface to each type of Picture class, a set of
classes: {Vaapi,V4L2}{H624,VP8,VP9}Picture is introduced. They are subclasses
of {H264,VP8,VP9}Picture classes and own {Vaapi,V4L2}DecodeSurface classes.

For VaapiVDA, the relationship is:

{H264,VP8,VP9}Picture
         ^    |
         |     -[owns] -> H264/VP8/VP9 specific metadata
      [is a]
         |
Vaapi{H624,VP8,VP9}Picture
              |
               -[owns]-> VaapiDecodeSurface
                           |
                            -[owns]-> common Picture metadata(visible_rect,...}
                                      platform-specific metadata(VASurface)

In case of V4L2VDA:

{H264,VP8,VP9}Picture
         ^    |
         |     -[owns] -> H264/VP8/VP9 specific metadata
      [is a]
         |
V4L2{H624,VP8,VP9}Picture
              |
               -[owns]-> V4L2DecodeSurface
                           |
                            -[owns]-> common Picture metadata(visible_rect,...)
                                      platform-specific metadata:
                                        ({input,output}_record, config_store...)

However, as {Vaapi,V4L2}{H624,VP8,VP9}Picture are platform-specific already,
we can eliminate one level of ownership indirection by removing
{Vaapi,V4L2}DecodeSurface classes, as well as avoid having the same common
Picture metadata in each of the 6 {Vaapi,V4L2}{H624,VP8,VP9}Picture classes
to further simplify the design:

   CodecPicture
         ^    |
	 |     -[owns] -> common Picture metadata
      [is a]
	 |
{H264,VP8,VP9}Picture
         ^    |
	 |     -[owns] -> H264/VP8/VP9-specific metadata
      [is a]
	 |
Vaapi{H624,VP8,VP9}Picture
              |
	       -[owns] -> platform-specific metadata(VASurface)

Moreover, this will further allow us to reuse the picture classes on all
levels of the hierarchy (including {V4L2,Vaapi}{H624,VP8,VP9}Picture
classes) for the upcoming, new AcceleratedVideoEncoder framework, without
having to create a new set of encoder-only {Vaapi,V4L2}EncodeSurface classes.

Removal of V4L2DecodeSurface is left for a follow-up CL.

BUG=703988
TEST=VDA unittests, video playback in Chrome, video playback in ARC++

Cq-Include-Trybots: luci.chromium.try:linux_optional_gpu_tests_rel;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: I86f30adf4b5754fffb89eb3769b11d01d8e04814
Reviewed-on: https://chromium-review.googlesource.com/947545
Commit-Queue: Pawel Osciak <posciak@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Kuang-che Wu <kcwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543995}

Unused for over a year, since:
  https://chromium.googlesource.com/chromium/src/+/a5466f457a195abd0f03066439c0efae3b5e14b0

Change-Id: Ie04f64f9156b71aa78dc498c70997cccbc7817aa
Reviewed-on: https://chromium-review.googlesource.com/966541
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Reviewed-by: Yuta Kitamura <yutak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543994}

This reverts commit 827ddeb7.

Reason for revert: crbug.com/823119

Original change's description:
> cc: CHECK surface invariants in LayerTreeHost on all platforms
>
> This is an option now that aura::WindowTreeHost have been fixed
>
> Bug: 818085
> Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
> Change-Id: I074ade34758a5005862543549e4bbe69838301b9
> Reviewed-on: https://chromium-review.googlesource.com/959550
> Commit-Queue: ccameron <ccameron@chromium.org>
> Reviewed-by: Fady Samuel <fsamuel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543656}

TBR=ccameron@chromium.org,fsamuel@chromium.org

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

Bug: 818085, 823119
Change-Id: Ib0e66b23c1fb3420a2a6d38e17255e7b01b9e803
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/968161
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543993}

This reverts commit 6af9df3e.

Reason for revert: Caused a regression as outlined in
https://chromium-review.googlesource.com/c/chromium/src/+/957265#message-bfd66cb6916d1397f05a74dd7c1fca4645857147

Original change's description:
> Enable ClientHintsPersistent feature (Accept-CH-Lifetime header).
>
> blink-dev i2s thread: https://groups.google.com/a/chromium.org/d/topic/blink-dev/8RBFue7RMXQ/discussion
>
> Change-Id: I5595b3aed72ea0cece88948f69f480f5808fce6b
> Bug: 735518,782381,816661
> TBR: raymes@chromium.org
> Reviewed-on: https://chromium-review.googlesource.com/957265
> Reviewed-by: Tarun Bansal <tbansal@chromium.org>
> Reviewed-by: David Dorwin <ddorwin@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Commit-Queue: Tarun Bansal <tbansal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#543786}

TBR=ddorwin@chromium.org,raymes@chromium.org,kinuko@chromium.org,tbansal@chromium.org

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

Bug: 735518, 782381, 816661
Change-Id: I47c42057e7d3158eeb515b993266ce0ff8e937e7
Reviewed-on: https://chromium-review.googlesource.com/968081
Commit-Queue: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543992}

Since Blink doesn't like |bool| parameter, we change
Pasteboard::WriteHTML() to take |SmartReplaceOption| for more clearly
to understand the parameter.
This CL can help us in [1] to get rid of CanSmartCopyOrDelete() in
|ClipboardCommands|.

[1]: http://crrev.com/c/948243Signed-off-by: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I340ed1c6eefa90b6f72a181811ea28ede938b9d3
Reviewed-on: https://chromium-review.googlesource.com/965864Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543991}

We recently re-implemented auto-expansion of notification
(crbug.com/810656), but it sometimes caused some junkness
while animation when it was auto-expanded. That was because
auto-expanded is done in the final phase of layouting.

This CL moves the auto-expansion to earlier phase:
- (on add): just before the view is added to the list
- (on update): just before the view is updated in the list
- (on remove): just after the view is removed from the list

Bug: 810656
Test: manual
Change-Id: I015f45f74eef37f89f11edc1b3b346d18771862c
Reviewed-on: https://chromium-review.googlesource.com/958757
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543990}

https://chromium.googlesource.com/chromiumos/platform/system_api.git/+log/1e83c2514884..72bfdd343136

$ git log 1e83c2514..72bfdd343 --date=short --no-merges --format='%ad %ae %s'
2018-03-07 amoylan Add DBus service constants for ML Service
2018-03-13 jkardatzke Add StartContainer D-Bus call for vm_concierge
2018-03-09 derat system_api: Delete power_manager::kBrightnessChangedSignal.
2018-03-07 allenvic smbprovider: Add GetSharesOptionsProto

Created with:
  roll-dep src/third_party/cros_system_api

Bug: 813699
Change-Id: I2079dbd81a3dd3ee0e6ba0e89b0f4b1c12e0fe7d
Reviewed-on: https://chromium-review.googlesource.com/967982Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543989}

Bug: 803774
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I0d523903974747847bb2863e22d9bfa2e148a50a
Reviewed-on: https://chromium-review.googlesource.com/961821
Commit-Queue: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543988}

The inline settings should be triggered by mouse long click.

BUG=818734
TEST=manual

Change-Id: Iab3c522e86a187bef92276bb5776f0937bbd75ae
Reviewed-on: https://chromium-review.googlesource.com/962556Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Megumi Hattori <megumihattori@google.com>
Cr-Commit-Position: refs/heads/master@{#543987}

https://skia.googlesource.com/skia.git/+log/a7b84c5a50da..4410d7ff7572

$ git log a7b84c5a5..4410d7ff7 --date=short --no-merges --format='%ad %ae %s'
2018-03-19 update-docs Update markdown files

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

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

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

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

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

This CL removes the API getContext(), and has all the callsites
either use container view's context (for Chrome) or use
the context directly (WebView). Content layer internally uses
the ContentViewCoreImpl.getContext() which now becomes private.


Bug: 598880
Change-Id: I035454b0eb488646dad5bdaf963d6de1cd29ca86
Reviewed-on: https://chromium-review.googlesource.com/965701
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543984}

Produce classes for custom elements by eval() and string concatenation.

Change-Id: I834a3eb8abbcc4bc36646d63215b86f415ec8da9
Reviewed-on: https://chromium-review.googlesource.com/968001Reviewed-by: Takayoshi Kochi <kochi@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543983}

This patch makes |Selection#{base,extent}{Node,Offset}| as aliases of
|Selection#{anchor,focus}{Node,Offset}| instead of getting position from
|VisibleSelection| which we don't want to expose to JavaScript.

Note: Selection#{base,extent}{Node,Offset} are not standard API and there
are some discussion for standardizing them[1].

[1] https://github.com/w3c/selection-api/issues/34
Specify baseNode/baseOffset/extentNode/extentOffset?

Bug: 701501
Change-Id: I34fcdb4e80d5cef49bc1e0bdaea3cdec5c8b3758
Reviewed-on: https://chromium-review.googlesource.com/965663Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543982}

BUG=762641
TBR=jennyz@google.com

Change-Id: I41d3bc792dd4ee541088f8688ea1b4baca7cfe09
Reviewed-on: https://chromium-review.googlesource.com/967665Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543981}

Add support & tests for (min/max)-(width/height).

Note that the typed om spec specifies the old specs for these properties:
https://drafts.csswg.org/css21/visudet.html

Bug: 820299
Change-Id: I9c65f7f24d84b83ea2e2f167f8fb86be967eff06
Reviewed-on: https://chromium-review.googlesource.com/968003
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543980}

Make RenderingHelper::QueueVideoFrame() behave properly in the case that
the requested fps is 0. This allows us to drop a GLRenderingVDAClient
parameter and simplify the logic of the vdatest a bit.

BUG=819542
TEST=Verified that vdatest was still passing on eve, hana and kevin

Change-Id: I500a693d9834cc3791ff5213bfd8e7cc0cc92bbe
Reviewed-on: https://chromium-review.googlesource.com/954769Reviewed-by: Wu-Cheng Li <wuchengli@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543979}

This change is required for adding input streams in audio service, in which case AIC will be created on audio thread.
Other changes:
* replace creation thread with sequence.
* refactor unittests, add tests for CreateForStream and SetVolume.

Bug: 803102
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: I2aa61b44a78369590892d88899221d29d18927ab
Reviewed-on: https://chromium-review.googlesource.com/952451
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543978}

This is part of efforts to replace base::ThreadTaskRunnerHandle::Get()
and SequencedTaskRunnerHandle::Get() with other appropriate task runners
in the renderer.

Bug: 786332
Change-Id: I2069aba52ec65f4ff6fd7cda0f7c437f072eac89
Reviewed-on: https://chromium-review.googlesource.com/965902Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543977}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/d49af833556c..8d50e94a5bc9

$ git log d49af8335..8d50e94a5 --date=short --no-merges --format='%ad %ae %s'
2018-03-18 manojgupta chromite: Fix a bug in fuzzer gs_path.

Created with:
  roll-dep src/third_party/chromite
BUG=822517


The AutoRoll server is located here: https://chromite-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=chrome-os-gardeners@chromium.org

Change-Id: Ia4cd4492e1197f1942fcc6b91dfa489f50de2a3b
Reviewed-on: https://chromium-review.googlesource.com/966500
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#543976}

This patch adds support for motion path properties. We had to modify
the computed style computation for <position> values. Previously, we
parse a <position> value as a CSSValuePair, but compute them to a
CSSValueList containing two items. This is very strange, so we just
compute to a CSSValuePair. Since both serialize to the same string,
this has no behavioural changes on CSSOM.

Bug: 820299
Change-Id: I2131055dad0785eb47ea2d2d89f00229f4376bae
Reviewed-on: https://chromium-review.googlesource.com/967915Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543975}

This calls it from OnLayerTransform(). That way, if the transform is
changed outside of Window::SetTransform, everything still works.

BUG=822917
TEST=covered by tests

Change-Id: I27acb266c4a4993df0a71457af8aa3b4c2cde5d1
Reviewed-on: https://chromium-review.googlesource.com/967841Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543974}