GitLab

Extensions code wants to run scripts on the initial empty document,
so instead of adding a duplicate call to all ContentRendererClients
(both RenderFrameCreated and RunScriptsAtDocumentStart) we can have
the extensions code do the right thing with the RenderFrameCreated
signal.

R=dcheng@chromium.org, reillyg@chromium.org

Bug: 1158869
Change-Id: I11a969e8b84933f13a5ceadb6e6d3943a5fb5d9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627690Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844203}

The test is flaky on all platforms:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=LoadTimingBrowserTest.HTTPS&testType=browser_tests

TBR=ryansturm@chromium.org

Bug: 1128033
Change-Id: I5de88f598d93ff43f06a617a9713d95375698775
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633684
Commit-Queue: Yi Gu <yigu@chromium.org>
Auto-Submit: Yi Gu <yigu@chromium.org>
Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844202}

Based on Søren's sample code in http://b/176818423.

D8's java API allows us to determine the exact set of dependencies that
a class in the current target depends on to desugar correctly (generally
its superclass(es) and interface(s) it implements). The class would only
need to be re-desugared with D8 if one of these dependencies changes.

This CL makes use of this information in a less granular way. If any jar
containing one of these dependencies is changed, then we re-dex all the
classes. Even so, this limited reduction in dependencies from using D8
for desugaring reduced the previous regression from +50% to +10% for the
base_java_sig benchmark.

Follow-up CLs will attempt to make use of the more granular desugar
dependency information to further improve the timing of D8 desugar. For
the time being, we are continuing to use bazel desugar.

Bug: 1015559
Change-Id: If507a4013af7bed0820758629a4b9db69942727b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2621928
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844201}

The test is flaky.

TBR=kmarshall@chromium.org
Bug: 1167266

Change-Id: I1a788509d7bb69439549358f6a8ef651a38526d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633841Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Auto-Submit: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844200}

This CL starts running lacros tast tests on the builder:
chromeos-amd64-generic-lacros-chrome.

Bug: 1158590
Change-Id: I2336084746548f8db6d2596ced7768c9c1088cab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2622344Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844199}

This CL changes `scroll_offset_at_last_raster_`, `scroll_offset_`, and
BoundScrollOffsetToDocument() from pp::FloatPoint/pp::Point to
gfx::PointF/gfx::Point, so that they can be migrated to
PdfViewPluginBase later.

Bug: 1101101
Change-Id: Iaa845e45b7d6a1d735fb44de3f7194df43b0f32f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626926
Commit-Queue: Hui Yingst <nigi@chromium.org>
Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Reviewed-by: K. Moon <kmoon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844198}

The existing name is somewhat peculiar - the new name better describes
the CSS syntax being parsed.

Change-Id: Ief212daa9e910b9a148f9946206e25f18cc2c81e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632690
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844197}

Bug: 1164469
Change-Id: I0fab507f0a58676abd0143e5bb8ea562bfb113f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628083
Commit-Queue: Peter Kvitek <kvitekp@chromium.org>
Reviewed-by: Peter Kvitek <kvitekp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844196}

See linked bug for details.

TBR=ellyjones@chromium.org

Bug: 1167249
Change-Id: I97c11cc0eab2c1eba5ed38182befb1bc22d0d7e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633350
Commit-Queue: Yi Gu <yigu@chromium.org>
Auto-Submit: Yi Gu <yigu@chromium.org>
Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844195}

Bug: 1075649
Change-Id: Ia308f0fdd33e274921b1519c5f1aa539da775360
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627777Reviewed-by: Caroline Rising <corising@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844194}

Bug: 1147581
Change-Id: I291f529cbb1686c6135791b99268f3cb310d4c98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587562Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844193}

Bug: 1136102
Change-Id: I6fe26dbf5f0c83672136aebe8f4a50846b4cc559
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633347Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Shuran Huang <shuuran@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844192}

In ChromeVox background page on startup via console:
Error: Failed to load resource: net::ERR_FAILED
From chrome-extension://invalid/
(repeated 43 times).

The underlying sre_browser.js packed js script is making failed
XMLHttpRequest calls, blocked by CORS policy.

R=akihiroota@chromium.org

Bug: none
Change-Id: Id2d46ab3976dfc5b85d993403d587e85d4c66600
AX-Relnotes: n/a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632869Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844191}

Adds people who are now responsible for Desktop PWAs as the rightful
owners, and a few other changes.

Change-Id: I7e76fb4d5902ded0a2d422ede66f440c4db48a05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409894
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Auto-Submit: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844190}

Update the stored type of inner multicols with pending OOFs added in
CL:2612392 from NGBlockNode to LayoutBox*. This was requested as it
makes converting NGBlockNode to a GarbageCollected class easier.

Bug: 1079031
Change-Id: If2bf19de5774b7f003650b2c8f923cba4adfbe3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630730
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Yuki Yamada <yukiy@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844189}

This CL fixes an issue with the UI not being updated after the profile loads and the policy becomes available. Now after a callback about profile creation is called, updating mic visibility is requested.

Testing this change: I didn't test it end to end with my own policy server, I did it in a somewhat hacky way with a bool variable that was flipped in the callback to make sure that UI is updated.


Bug: 1161022
Change-Id: I4fc8ab9067044b9198efaba0b94acf0199504492
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623164Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Josh Simmons <jds@google.com>
Commit-Queue: Basia Zimirska <basiaz@google.com>
Cr-Commit-Position: refs/heads/master@{#844188}

Unittests rely on ScopedFeatureList which does not work
because of these static values.

Bug: 1166714
Change-Id: Ie3b0ff8beac1efa2398c68e77725ff69fce9cc2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627405
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844187}

Child bubbles have padding and child spacing such that there are gaps
between holding space sections and child bubble edges as well as gaps
between holding space sections within the same child bubble.

Moving selection clearing to child bubbles instead of section views
eliminates what the user might otherwise perceive as dead spots.

Bug: 1167248
Change-Id: I561f2862258189fa9960d6c25de7bd6da124771a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632808Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#844186}

TBR: yusufo@chromium.org
Bug: 1157892
Change-Id: I6199dacb72f3e9e9133d28115a7a621a8c0297fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613954Reviewed-by: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844185}

BoringSSL recently added Neon and hardware crypto optimization
support for the Windows on Arm (WoA) platform.

Enable use of these optimized functions in the Chromium BoringSSL
BUILD.gn file.

Change-Id: Ic5229f73f3a52bdb291f68819f4cb6862e1c4798
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632753Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844184}

Change-Id: I5fbffa18e477d5e24fe3a772f1ed97f92d9b985e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573678
Commit-Queue: Renjie Tang <renjietang@chromium.org>
Reviewed-by: David Schinazi <dschinazi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844183}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-mac-chromium-autoroll
Please CC bsheedy@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: bsheedy@chromium.org
Change-Id: I445ae1f4b5cb389bb1280fda96dd53400aa53633
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633444Reviewed-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@{#844182}

This CL removes dead code related to legacy supervised users and
renames TODO(crbug/866790) to TODO(crbug/1155729), which is the main
bug for tracking legacy supervised user code removal.

Bug: 866790
Change-Id: I7ece1ef3e9f4dd548d8f3387d98082f490030d12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626194Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Dan S <danan@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Dan S <danan@chromium.org>
Auto-Submit: Toby Huang <tobyhuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844181}

This reverts commit e2f3b551.

Reason for revert:

Breaks local user flow when entering chrome_sdk

ERROR at //build/config/chromeos/rules.gni:180:11: Undefined identifier.
          _symlink_targets[2],
          ^-----------------
See //chromeos/BUILD.gn:239:3: whence it was called.
  generate_runner_script("cros_test_wrapper") {
  ^--------------------------------------------
See //BUILD.gn:442:7: which caused the file to be included.
      "//chromeos:chromeos_unittests",

Original change's description:
> Lacros: create lacros tast test targets
>
> This CL creates gn targets for lacros tast tests, and the main
> motivation is to run lacros tast tests on Chromium CI.
>
> Bug: 1158590
> Change-Id: I783779c3386a39743b8227367189b0b87832b9dc
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2606188
> Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
> Reviewed-by: Ben Pastene <bpastene@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@google.com>
> Cr-Commit-Position: refs/heads/master@{#844127}

TBR=dpranke@google.com,liaoyuke@chromium.org,bpastene@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com

Change-Id: I1e51bf2e6aa97bfc40beba7d2693b68361cab2bc
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1158590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633782Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844180}

Instead of using one boolean value in profile pref to record
dismiss/restore state of cart module, this CL introduces two boolean
values to record whether the module is temporarily hidden or
permanently removed.

Bug: 1157892
Change-Id: I01d95a62fca6466ab893c7be8afbc20b5065ddf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625816Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844179}

Moving features to the Storage Service requires the ability to talk to
the Quota system via mojo. storage::QuotaClient is one of the interfaces
that needs to be mojofied.

Migrating all QuotaClient usage to mojo in one CL is risky, because this
CL would introduce timing changes to 7 storage systems (AppCache, Cache
Storage, File System, IndexedDB, NativeIO, Service Workers, WebSQL).
Therefore, QuotaClient will be migrated piece by piece.

This CL introduces the storage::mojom::QuotaClient interface, and
integrates it with QuotaManager. To facilitate a gradual migration,
QuotaManager will support both mojofied and non-mojofied QuotaClients.

QuotaManager tests will cover both types of clients, to ensure correct
operation throughout the migration. Other tests that integrate with
QuotaManager will use mojofied clients, because this reduces future
churn. To maximize test coverage, QuotaManager's support for mojofied
QuotaClients is written on top of the support for non-mojofied
QuotaClients.

This CL also adds TODOs documenting the cleanup that will be required
once all QuotaClients are mojofied.

Bug: 1016065
Change-Id: I6df5a97763447e41eb3b523e180a6c13dfa3199c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2610633
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844178}

Move GetPluginInfo to be a method on the PepperHost mojom object. This
code path is used for content layer (content shell is one example) to
load plugins. (chrome embedders use a ContentClient override).

Remove the now useless RenderFrameMessageFilter.

BUG=1157519

Change-Id: I0c1e4c74b86351169637b72c4224c9000ca70945
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630545
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844177}

These histograms are no longer used. The timing and count information is
already available into RenderText for every platforms. There is no need
to have a windows specific histograms.

R=robliao@chromium.org

Bug: 1151976
Change-Id: I0c90c44ace8f6607a55112a117a75cdd5b4eb20f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2611585Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844176}

This is a useful metric to monitor the adoption of the promo browser
commands.

Fixed: 1165094
Change-Id: I2df2e242cc072eb5ee74716a029eae111373584b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632065Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844175}

Bug: 1164846
Change-Id: I975c02ac34bb4e37a06ae7759eaffb7984f95065
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628024Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Chris Thompson <cthomp@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844174}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-linux-chromium-autoroll
Please CC bsheedy@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: bsheedy@chromium.org
Change-Id: Icc88c13289498fcfcc2c39167d5c81552bb2c8db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633171Reviewed-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@{#844173}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/3100aca993ac..1502a9ec072f

2021-01-15 vidorteg@microsoft.com [Loc] Migrate event_listener pane to Localization V2

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: chromium:1136655
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: Id2a9e3e8dfd61dd665a51c036a2f1ed4dae1f602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633134Reviewed-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@{#844172}

Bug: 1138595
Change-Id: I7b5ab3739842122e5b71f208b4e0bb237636ee3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2624608
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844171}

BUG=v8:9684

Change-Id: I724817e74370ecb3ef2f931fc16dc2324bd73629
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632612
Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
Auto-Submit: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844170}

Bug: 1155353
Change-Id: I1057fa0184ac79b6b28f1f0a863d6d630dc3f816
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630068Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844169}

The test is flaky.

TBR=atwilson@chromium.org
Bug: 1167239

Change-Id: I44c744fb99848edb28f63821e899b93e2993e41d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633093Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844168}

A page flip can result in a SWAP_NAK_RECREATE_BUFFERS signal,
indicating that the backing buffers must be recreated. Since the
buffers are entirely uninitialized, we should damage the entire
screen for the next draw [1].

Unfortunately, this doesn't work in SkiaRenderer because the GPU
thread performs the actual reallocation [2] and then posts a task to
the Viz thread to update the damage. The task taces with the next
invocation of DirectRenderer::DrawFrame, so there's no guarantee
that the new damage will be picked up in time for the next frame.
If it isn't, we will present a buffer with uninitialized data.

This CL fixes this issue by pausing SwapBuffer invocations after
reallocating buffers until we receive a frame with full screen
damage (e.g. the Viz thread catches up with the GPU thread).

[1] https://source.chromium.org/chromium/chromium/src/+/master:components/viz/service/display_embedder/gl_output_surface_buffer_queue.cc;l=263;drc=3c0194e7917daed5debe0d0772393e5784367e01
[2] https://source.chromium.org/chromium/chromium/src/+/master:components/viz/service/display_embedder/skia_output_device_buffer_queue.cc;l=458;drc=7ccffaf0933ccc647c744bf66971bcf5f33a676a

Bug: 1156182
Change-Id: Ibf0bf3d6903c4c4f2dadcfc71dfda36a03b513d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630227Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Brian Ho <hob@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844167}

Ensures subscribers know when a thumbnail is cleared, and avoids
sending them stale thumbnails from previous requests.

Fixed: 1163121
Change-Id: I31d881808fb2a6bb14ae20b7d5b2d67545b585c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628031Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Collin Baker <collinbaker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844166}

Bug: 1167232
Change-Id: I04177bb8c4cc7f0c31f8fe2a549f0ce837529b81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633094Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844165}

This fixes some path and test data issues that cause tests to fail
when enabling TFLite in the build.

This also creates a TFLite resolver for Chrome with the set of ops
to be supported initially.

Bug: 1165517
Change-Id: Ib0acdcb380578e94f4b7172b5ebe27ab6faafc25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631186Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#844164}