GitLab

It is an ODR violation for conflicting specializations for std::string to exist. Since
this is safe and reasonable, write a single std::basic_string<...> specialization in
cross_thread_copier.h to apply to std::string (and, should it come up in the future,
other specializations of basic_string).

Change-Id: I39b796aaf4c86edc00f46239da008e15110cebc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743100
Auto-Submit: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685483}

Bug: 49580
Change-Id: I9907d3ea7ccda4de77bcb800ff788255d3824057
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732674
Auto-Submit: Wez <wez@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685482}

Bug: 970031
Change-Id: I0c8800b3f4ded92230990817261f7212a0f49b50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730955Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685481}

There are only two callers, and one actually doesn't need SkData. Also
we can implement it only with SharedBuffer public functions. Hence this
CL removes the function.

Bug: None
Change-Id: I6709150b6e4b7708c161b3d83740f0cc7dfbcbd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743871Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685480}

No logic changes.
Updates enum values' names.

(acronyms are capitalized as single words, as per [1])
[1]: https://google.github.io/styleguide/cppguide.html#General_Naming_Rules

Change-Id: I4a73939546094fc6dcacfbc0753f85cc6dc683c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745549
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685479}

... where it is possible.

The remaining WebString occurrences in both files are because they
are still used in calls to public API methods.

BUG=704136
R=guidou@chromium.org, haraken@chromium.org

Change-Id: Iec1736d1911cf94b284beb1af677a9bd35ef98e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1744368
Auto-Submit: Antonio Gomes <tonikitoo@igalia.com>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685478}

As a preparation for updating the behavior according to the
draft spec, this CL adds spec comments and TODOs,
with some renaming and
aligning method boundaries with the spec concepts.

This CL doesn't change the behavior.

Bug: 990561
Change-Id: I79a995ef69c71a71f7aa6b11b78d64b2436163d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1734170
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685477}

Convert FilesMessage test by adding the files_message_unittest.html and
loading it from chrome://file_manager_test/. This test doesn't require
Polymer, however it was logging errors because of Polymer, this change
fixes Polymer in the test so no more log errors.

Restore the FilesToolTip test that was deleted on CL:1493332 because it
was incompatible with elements loading Polymer via
chrome://resources/html/polymer.html, now it's compatible again so
restoring it.

Using code from CL:1736348.

Bug: 991105
Change-Id: I908001c209f4291891b96714b3293ad5d86aca7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738506
Commit-Queue: Luciano Pacheco <lucmult@chromium.org>
Reviewed-by: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685476}

*** Note: There is no behavior change from this patch. ***

The PostTask APIs will shortly be changed to require all tasks to explicitly
specify their thread affinity, i.e., whether the task should run on the thread
pool or a specific named thread such as a BrowserThread. This patch updates all
call sites with thread affinity annotation. We also remove the "WithTraits"
suffix to make the call sites more readable.

Before:

    // Thread pool task.
    base::PostTaskWithTraits(FROM_HERE, {...}, ...);

    // UI thread task.
    base::PostTaskWithTraits(FROM_HERE, {BrowserThread::UI, ...}, ...);

After:

    // Thread pool task.
    base::PostTask(FROM_HERE, {base::ThreadPool(), ...}, ...);

    // UI thread task.
    base::PostTask(FROM_HERE, {BrowserThread::UI, ...}, ...);

This patch was semi-automatically prepared with these steps:

    1. Patch in https://chromium-review.googlesource.com/c/chromium/src/+/1635827
       to make thread affinity a build-time requirement.
    2. Run an initial pass with a clang rewriter:
       https://chromium-review.googlesource.com/c/chromium/src/+/1635623
    3. ninja -C out/Debug | grep 'requested here' | cut -d: -f1-3 | sort | \
           uniq > errors.txt
    4. while read line; do
         f=$(echo $line | cut -d: -f 1)
         r=$(echo $line | cut -d: -f 2)
         c=$(echo $line | cut -d: -f 3)
         sed -i "${r}s/./&base::ThreadPool(),/$c" $f
       done < errors.txt
    5. GOTO 3 until build succeeds.
    6. Remove the "WithTraits" suffix from task API call sites:

       $ tools/git/mffr.py -i <(cat <<EOF
       [
         ["PostTaskWithTraits",                            "PostTask"],
         ["PostDelayedTaskWithTraits",                     "PostDelayedTask"],
         ["PostTaskWithTraitsAndReply",                    "PostTaskAndReply"],
         ["CreateTaskRunnerWithTraits",                    "CreateTaskRunner"],
         ["CreateSequencedTaskRunnerWithTraits",           "CreateSequencedTaskRunner"],
         ["CreateUpdateableSequencedTaskRunnerWithTraits", "CreateUpdateableSequencedTaskRunner"],
         ["CreateSingleThreadTaskRunnerWithTraits",        "CreateSingleThreadTaskRunner"],
         ["CreateCOMSTATaskRunnerWithTraits",              "CreateCOMSTATaskRunner"]
       ]
       EOF
       )

This CL was uploaded by git cl split.

R=mgiuca@chromium.org

Bug: 968047
Change-Id: I9a6a855890e99daa22cbcae85322a7b76b470a17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728876
Auto-Submit: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685475}

As a step to reduce uses of Platform::Current()->GetDataResource,
this CL replaces all uses of Platform::Current()->GetDataResource
with UncompressResourceAsASCIIString in CSSDefaultStyleSheets class.
To do that, this CL introduces UncompressResourceAsASCIIString.

Bug: 983396
Change-Id: I4b37d98c5e129055431fc1622006f32607f5ecc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743868Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Cr-Commit-Position: refs/heads/master@{#685474}

This CL removes following two methods which were used for
on-the-main-thread service worker script fetch, which we don't
support anymore:

* CreateServiceWorkerNetworkProviderOnMainThread()
* CreateWorkerFetchContextOnMainThreadLegacy()

This CL also removes
ServiceWorkerNetworkProviderForServiceWorker as it was created
only from CreateServiceWorkerNetworkProviderOnMainThread().

Bug: 967272
Change-Id: I07d832302274cd16e60529740088bcc12cd03276
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745674
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685473}

Move current Chromium H264 accelerator to legacy and add support for
new H264 headers.
The use of new or legacy H264 accelerator is decided by whether the driver
supports request API or not.

BUG=chromium:987856
TEST=VDA unittest with test-25fps.h264 and frame validation on
     Minnie 3.14 and Kevin 4.4.

Change-Id: I103a0a8d08171ceb96f020c08125686d874ee41d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1723332Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685472}

Bug: 992224
Change-Id: I18ce6f9451838da185e29ca52e8d26144ad31402
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745108Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Shrek Shao <shrekshao@google.com>
Cr-Commit-Position: refs/heads/master@{#685471}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/24a749c4b23f..bfed8088cbab

git log 24a749c4b23f..bfed8088cbab --date=short --no-merges --format='%ad %ae %s'
2019-08-09 cjmcdonald@chromium.org parallel_emerge_new: Disable clean delay.
2019-08-09 cjmcdonald@chromium.org Use die_hook status file instead of PARALLEL_EMERGE_STATUS_FILE
2019-08-09 miahsanchez@google.com device_unittest: testing for remote command

Created with:
  gclient setdep -r src/third_party/chromite@bfed8088cbab

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: I71547435a7cff3d54721f1715261285559bc32b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745724Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685470}

We won't maintain on-the-main-thread script fetch
anymore.

Bug: 967272
Change-Id: Ie5a832bd10a361671b155ed0ffcf9b0bd0ef1085
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745667Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685469}

https://skia.googlesource.com/skia.git/+log/4d557e3df433..059bf776c184

git log 4d557e3df433..059bf776c184 --date=short --no-merges --format='%ad %ae %s'
2019-08-09 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 75efa7bb97a4..f046402b1480 (1 commits)

Created with:
  gclient setdep -r src/third_party/skia@059bf776c184

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=reed@google.com

Bug: chromium:None
Change-Id: Iee670c19e84657cbd38f446fd3672fd1e8dc34e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745723Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685468}

- NULL -> nullptr
- Class member initializers
- Member function renaming for readability

Bug: 896931
Test: No functionality change
Change-Id: I476a8c33c32468b692a375d56d9af82868732fda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1742689Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685467}

- upgrade_util.{cc,h} and friends are now only included in the build for
  relevant platforms (desktop Chrome).
- upgrade_util::SetNewCommandLine now explicitly takes ownership of its
  argument.
- A test seam has been added to RelaunchChromeBrowser. Tests may now
  specify a callback to be run when relaunch takes place.
- Unexpected calls to RelaunchChromeBrowser in browser_tests and friends
  now cause test failures (they previously attempted to launch Chrome).
- ScopedRelaunchChromeBrowserOverride is now available for tests of
  scenarios that involved RelaunchChromeBrowser.

BUG=958893,989468

Change-Id: I8620e2bbe56e282934b94b3ea2ae52ef32f9d04a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1736707
Auto-Submit: Greg Thompson <grt@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685466}

Bug: 980733
Change-Id: Ib9cedae07d1b2266f5384c57977dc05ff290d098
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1736445
Commit-Queue: Jinsong Fan <fanjinsong@sogou-inc.com>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685465}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c1956fdd863d..0f851e59ee6e


Created with:
  gclient setdep -r src-internal@0f851e59ee6e

The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll

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

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


CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None
Change-Id: I6f1d57c8b73bd82a04795b7ba61aaddc709a7588
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745829Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685464}

As we are adding ImageProcessor support to the V4L2SVDA, quite a bit of
code is going to be similar to the one already present in V4L2VDA. In
order to limit code duplication, move the most obvious bits into a
helper class for VDA which both classes can use.

Bug: b:132589320
Test: vdaunittest and vdatests pass on Minnie.
Change-Id: I6b0594b705acfd8f112335c9a56b3c262a5bca78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731510
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685463}

Start the IME service with an 'ime' sandbox when the build flag
ENABLE_CROS_IME_DECODER is true. This change is to help dev start
decoder engine easily.

By default, IME service will be started with a utility sandbox.

Bug: 837156
Change-Id: I7cefe8743298d713aeb257e48f3f7d9f9fca7564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743851Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Leo Zhang <googleo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685462}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/0d0f321a86b9..24a749c4b23f

git log 0d0f321a86b9..24a749c4b23f --date=short --no-merges --format='%ad %ae %s'
2019-08-09 miahsanchez@google.com device_unittest: testDryRunError.

Created with:
  gclient setdep -r src/third_party/chromite@24a749c4b23f

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: Id69feb9165261d118eec5ff0daa60dd197abf3d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745830Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685461}

UncompressResourceAsString() decoded a resource blob as UTF-8, and
AddString() in chooser code encoded it as UTF-8 again. We should just
copy the blob as binary.

Bug: 983396
Change-Id: I10c87d1f984d5780698787b45fd2444a862bb655
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745677Reviewed-by: Gyuyoung Kim <gyuyoung@igalia.com>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685460}

This CL instantiates the ExternalWebAppManager and WebAppPolicyManager
subsystems when BMO is enabled. These subsystems are generalised to work
with or without BMO and are needed for general web app operation.

This CL also reorders the subsystems to be alphabetical in the header and
ordered by their interdependencies in the initialisation code.

Bug: 916381
Change-Id: Ie0f146c41bde8355243e0b380dee5e1c642596e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745672
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685459}

page_cycler_v2 is replaced by loading.desktop.

Bug: 868755
Change-Id: Ia4650a92e85f9c60f99d8647ca0bf291b1ceee60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743849Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Kuo-Hsin Yang <vovoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685458}

- Web Share spec has moved from WICG to W3C.
- Updated some Web Share Target URLs to point to the WICG spec, not the
  explainer.
- Updated some Web Share Target URLs to point to the WICG spec, not a
  draft on the pr-preview site.
- Removed some notes that say Web Share Target is part of an unlaunched
  experiment.

Change-Id: I48132388192d773d962d13bc9361778ddeb66e4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1742258Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685457}

As we are planning to add IP support, GL fences will not always be
associated to decoder buffers - if the IP is in use, then the fence will
refer to the IP buffer and we must thus prevent it from being used for
processing again.

However, the way GL fences management is done is to wait on a fence
before queuing a decoder buffer. This CL addresses this by using a FIFO
queue of GL fences which retain their associated decode surface with
them. Since the IP buffer will be tied to the decode surface, this means
it will be kept for as long as required.

This design is similar to what was done in the V4L2VDA to address the
same situation.

Bug: b:132589320
Test: vdaunittest and vdatests pass on Minnie.
Change-Id: I06ba55d995a5ba3bc9fc09fcc4b2358987294eb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1741431
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685456}

FilterAndResizeIconsGenerateMissing unifies icon stuff for user-initiated and
sync-initiated installs.

Some utils in web_app_install_utils.h becomes private: hide them in .cc
file in anonymous namespace.

This CL just moves the code, no behavior changes.

Bug: 973288
Change-Id: Id332641c5317a54ef0f0ee06f9347f558672925d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743239Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685455}

Previously, mapping buffer data between the Dawn client and service
required additional copies. The client had to keep a shadow copy of the
buffer data, copy it into the command stream, and then the service would
copy it out. Implementing the dawn_wire MemoryTransferService with
shared memory completely removes the additional copies because the data
is visible to both the client and service.

Bug: dawn:156
Change-Id: I31e4c005a1b26ff5a1bf8139bb164d2dcabc48ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713751
Commit-Queue: Austin Eng <enga@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685454}

Bug: 969558
Change-Id: I1ccb9489e4cc263140950a67fad3b7b03b3a0684
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743108
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Reviewed-by: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685453}

BUG=990462

Change-Id: I5c7c430a742f763b9a9e350cc3ffe262fe2d0b33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745679
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685452}

The kCrostiniAppUninstallGui feature was turned on by default in M76 so we no
longer need this feature.

Bug: 955797
Change-Id: I559149a37b8415ef67dc82cd2bac92456ad65817
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743297
Auto-Submit: Timothy Loh <timloh@chromium.org>
Commit-Queue: Nic Hollingum <hollingum@google.com>
Reviewed-by: Nic Hollingum <hollingum@google.com>
Cr-Commit-Position: refs/heads/master@{#685451}

https://chromium.googlesource.com/angle/angle.git/+log/c9ba782a6fd4..eb0479e245f0

git log c9ba782a6fd4..eb0479e245f0 --date=short --no-merges --format='%ad %ae %s'
2019-08-08 cnorthrop@google.com Vulkan: Texture 3D and 2DArray layers as framebuffer attachments
2019-08-08 jmadill@chromium.org Vulkan: Correct generated shader paths.

Created with:
  gclient setdep -r src/third_party/angle@eb0479e245f0

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Bug: None
Change-Id: Ie31762c00c2290fc5f14dda489982597005d72c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745322Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685450}

This patch implements more of |NGFragmentItemsBuilder|, so
that |NGFragmentItems| are created and stored to
|NGPhysicalBoxFragment|, except out-of-flow objects.

Not all necessary changes are in yet, but instantiations of
most objects and call flows are in place.

The new code still relies on |NGPhysicalLineBoxFragment| and
|NGPhysicalTextFragment|. |NGFragmentItem| is supposed to
deprecate them, but eliminating them is not very easy. After
some experiments, I'm planning to create |NGFragmentItem|
first from these fragments, but plan to eliminate them as the
code grows. |NGPhysicalTextFragment| is probably easy, but
|NGPhysicalLineBoxFragment| may take a while as it is used
for communication and propagation between
|NGBlockLayoutAlgorithm| and |NGInlineLayoutAlgorithm|.

Bug: 982194
Change-Id: Icc2d4716d4c351bd3b8810fbeac77ba48c118d3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739033
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685449}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=cmasso@chromium.org

Change-Id: I01039a3f783214c4b6457109b0671d33d0acf383
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745435Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685448}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/fd8f7d66cc6f..c1956fdd863d


Created with:
  gclient setdep -r src-internal@c1956fdd863d

The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll

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

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


CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None,chromium:None
Change-Id: I707e40c5b0dac76b126058a68dccb2908e76c144
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745320Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685447}

https://dawn.googlesource.com/dawn.git/+log/42e1bba480d1..ef2fac0b9447

git log 42e1bba480d1..ef2fac0b9447 --date=short --no-merges --format='%ad %ae %s'
2019-08-09 iannucci@google.com [infra/config] Bump OS X SDK version for dawn.
2019-08-09 enga@chromium.org MemoryTransferService: Separate functions to serialize and get serialization size

Created with:
  gclient setdep -r src/third_party/dawn@ef2fac0b9447

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

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

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


CQ_INCLUDE_TRYBOTS=luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
TBR=cwallez@google.com

Bug: chromium:973721
Change-Id: Ia452ea580eb976bdde546ba34ac9d0756276137d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745321Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#685446}

It's reaching the 1hr timeout in some shards:
https://ci.chromium.org/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/14512
https://ci.chromium.org/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/14509

Bug: 865455, 992200
Change-Id: If55fae6dc0151358d8e4b81b7d69261c2e45decb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745589Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Ben Pastene (OOO on the 9th) <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685445}

This CL implements the first part of the scheduler API prototype:
1) Adds IDL and classes for Task, TaskQueue, and Scheduler.
2) Adds window.scheduler instance tied to the Document's lifetime.
3) Implements basic postTask() related functionality:
  - Scheduler.postTask()
  - Scheduler.taskQueue()
  - TaskQueue.postTask()
  - TaskQueue.priority
  - Task.priority
  - Task.status
  - Task.cancel
4) Adds web_tests for the functionality in (3).

For additional context, see the explainer
(https://github.com/WICG/main-thread-scheduling/blob/master/PrioritizedPostTask.md) and
the API proposal/design doc
(https://docs.google.com/document/d/1xU7HyNsEsbXhTgt0ZnXDbeSXm5-m5FzkLJAT6LTizEI/edit?usp=sharing).

Bug: 979017
Change-Id: If49c4cbdc042c80f28797ad94876d3cde8f9411f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1703091
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685444}