GitLab

https://android.googlesource.com/platform/external/perfetto.git/+log/87ede8895026..2e43102c54d1

git log 87ede8895026..2e43102c54d1 --date=short --no-merges --format='%ad %ae %s'
2019-10-18 lalitm@google.com trace_processor: add benchmark for RemoveIf and UpdateSetBits

Created with:
  gclient setdep -r src/third_party/perfetto@2e43102c54d1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@google.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/+/master/autoroll/README.md

TBR=perfetto-bugs@google.com

Bug: chromium:135177627
Change-Id: Iecb2ff41cb5e9d0fae3194de79c96c6f6c41ee7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869252Reviewed-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@{#707398}

This change removes an unnecessary update to children of
<input type="text"> elements when any attribute is modified on the
element.

A similar patch was made in WebKit here:
https://trac.webkit.org/changeset/208653/webkit

In the WebKit patch, the update still occurs if the attribute is "value"
or "placeholder." We already handle "value" attribute changes in a case
in HTMLInputElement::ParseAttribute, and we already handle "placeholder"
attribute changes in TextControlElement::ParseAttribute. Since we handle
those cases explicitly, we can remove the entire AttributeChanged
function.

Bug: 1012774
Change-Id: Ib75fde9c5b3e1f9eea4232bf5bfa915d573b9c7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865658Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707397}

Replacing calls to global device_emulator.bluetoothSettings methods with
WebUI events and FireWebUIListener().

This is in preparation of migrating this page to Polymer3.

Bug: 1015241
Change-Id: I3d8bc7f5b008e734670393c0832f741f13195e1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868089Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707396}

This reverts commit 916c54c5.

Reason for revert:
abDragTabSharingUIViewsBrowserTest.DragTab and
TabDragTabSharingUIViewsBrowserTest.DragSharedTab fail on linux-chromeos-rel
https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-rel

Original change's description:
> Add browsertests for tab sharing UI views.
> 
> Add tests to verify tab sharing UI elements: infobars, contents border
> and tab sharing indicator.
> 
> Bug: 996722
> Change-Id: I5fa5ec7e4a48a66c1ba9b08ff76b84a105961352
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847287
> Reviewed-by: Guido Urdaneta <guidou@chromium.org>
> Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#707368}

TBR=guidou@chromium.org,marinaciocea@chromium.org

Change-Id: I3e000bbd82d3fe3f78684d200cb2c10b4171328e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 996722
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869116Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707395}

BUG=987646

Change-Id: I41920758c20b88c0a20a609286a2203c4be2fce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865404
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707394}

When changing the resolution while decoding and using video decoder,
VIDIOC_S_FMT on the output buffer will return EBUSY.
Before changing the output buffer format, the capture buffer must be
destroyed.
This patch, moves the capture buffer destruction before changing the output
buffer's format as per specification [1].

[1] https://hverkuil.home.xs4all.nl/codec-api/uapi/v4l/dev-stateless-decoder.html#dynamic-resolution-change

BUG=b:142828922
TEST=ran tast with video.DecodeAccelVDVP8ResolutionSwitch on veyron_minnie-kernelnext.
TEST=ran tast with video.DecodeAccelVDH264ResolutionSwitch on veyron_minnie-kernelnext.
TEST=ran tast with video.DecodeAccelVDVP8 on veyron_minnie-kernelnext.
TEST=ran tast with video.DecodeAccelVDH264 on veyron_minnie-kernelnext.
Signed-off-by: Francois Buergisser <fbuergisser@chromium.org>
Change-Id: I304cd4b7e52d95bec4dcf4bcb803439c6f8cf273
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868574
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707393}

Bug: 1014652
Change-Id: I522701fb329af27600ba038b7f6c7b6bb205fa10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866859Reviewed-by: Peter Lee <pkl@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707392}

... for regular profiles.

Additionally:
 - Make heading clickable and link to 'Edit person' page.
 - Remove identity title when profile is not signed-in.
 - Add horizontal margin to identity text.

Screenshot:
https://drive.google.com/file/d/1y4ewSqp2Uw3c4DFH3HgwspOS8a4u0i5C/view?usp=sharing
https://drive.google.com/file/d/1IK4tjzTewrTd-Ane9forYL377538IvBL/view?usp=sharing

Bug: 995720
Change-Id: I608fdc7a6d6aec31def7f8bfde1f9ef355c4de16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868876Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707391}

This CL switches the order notifying all contexts about context loss and
restarting the GPU process for the exit_on_context_lost GPU driver bug
workaround. This will ensure the contexts are lost before the process
exists.

Also add an early out so no new GPU channels are created while the GPU
process is exiting. There is no point in creating new GPU channels at
this point as it can only cause problems.

Bug: 1011420
Change-Id: I10294074cc9f2f087124f1cb68fedf22ed364a3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866408
Commit-Queue: kylechar <kylechar@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707390}

- Changes very large code entry writing to create an indirection. The
  first entry is double-keyed just like other size entries. However, it
  contains response time, size, and a hashed checksum of the data. The
  checksum is used as a second key for another entry that contains a
  no header and the actual code.
- Changes very large code entry fetches to do a double-keyed read as
  before. If there is a checksum in the header, that is used as a
  second key to read the actual code.
- Every origin that loads a given resource for the first time will
  get a cache miss. To get a cache hit, the origin must first generate
  code and write it to the cache. The code is checksummed using SHA-256
  to make it very unlikely for a malicious origin to store its code to
  the same key as another origin. Origins that generate identical code
  share the same code entry.

Design Document:
https://docs.google.com/document/d/1SCH15oCFJW55jsTJZ0T7XAQIZVryI_IJOIENyL_q4n4/edit

Bug:chromium:936107

Change-Id: If99d2dada102382d51f97286fb3e5d9d2faf3aa6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846102
Commit-Queue: Bill Budge <bbudge@chromium.org>
Reviewed-by: Mythri Alle <mythria@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707389}

- The parameter order of manufacturer was flipped

Bug: 1009454
Change-Id: Ia2bdcf4acb9693a7deab083c535db3f474337aab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866728
Auto-Submit: Alex Chau <alexchau@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707388}

This CL moves PerformBatchOperations() out of the responsibility of
WebStateList serialization and into the caller's responsibility.

This allows callers to define what a batch operation is. For example,
when restoring closed tabs, a batch operation includes modifying
TabRestoreService at the same time as adding WebStates to the WebStateList.

Note: PerformBatchOperation was recently added to web_state_list_serialization
in this CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1865161

Bug: 1014526
Change-Id: I40b11e4fe9b30a5fe18e0e8e404c298b04676d1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867389
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707387}

Using wpt-import in Chromium 34a196e3.
With Chromium commits locally applied on WPT:
6386d9d8 "Update service_worker_unregister_and_register()"
1d5b803f "Add WebVTT support for inline styling - Web Platform Tests"
ba49a3d6 "autofocus: Change the timing of 'flush autofocus candidates'"


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

NOAUTOREVERT=true
TBR=lpz

No-Export: true
Change-Id: I117e86fa0e271dc3c885853c57da6e77f65e901c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869349Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#707386}

When applyConstraints is called on a track, the capabilities are limited
to what the settings already set on the track. This also means that the
constraints algorithm needs to guarantee that the same
processing-properties type is selected.

So far, we have done so by allowing a single processing-properties group to
be initialized when the capabilities are set. This approach is, however,
incompatible with applyConstraints reconfiguration.

This CL guarantees the same requirements, but simplifying the logic and
always initializing all the processing-based groups for processing. It
also adds the possibility to inspect the processing type selected by
returning the extra field when the select-settings algorithm is run.

BUG=796964

Change-Id: Ib34f7d33eb3aa8e1460aebcda20941df0503fa62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847275
Commit-Queue: Armando Miraglia <armax@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707385}

This CL was partially created by
//base/android/jni_generator/jni_refactorer.py.

The conversion also required converting unit tests to use the new JNI
mocking approach provided by JniMocker.

Bug: 929661
Change-Id: I57cc3e19641af73e745ea1b224947586ba2287bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834035
Auto-Submit: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707384}

Also add NetworkService API to enable partitioning auth cache entries
by NetworkIsolationKey, and a field trial to set it to true. All done
in one CL to allow integration testing.

Bug: 993806
Change-Id: I323826847cda68e0e1acd776dc6ba260743d3952
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865411
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707383}

Adding an API that will refresh (refetch) Enterprise Policies when called.
This will remove the need for automated testing to go to the
chrome://policy page, and "click" the refresh button via a js call.

Bug=chromium:1012712
Test=Locally deployed and tested and basic unittest.

Change-Id: Iedc3c2e349cceb7f8b076259877d548b9f4babda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1683103
Commit-Queue: Derek Beckett <dbeckett@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707382}

Some of the SyncEncryptionHandler APIs are about decrypting pending
keys, but the keys themselves should NOT be added directly to the main
cryptographer, to avoid leaking keys accidentally (or wrong ones).

Instead, let's use temporary keybags to decrypt pending keys.

Bug: 922900
Change-Id: Ie7af21ce7dccdc1422e3b4375f9519b5835ea379
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866829Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707381}

This will fix the breakage of go/wpt-waterfall and resume running tests.

Bug: 996842
Change-Id: I1df7072de6f344c846cffa044b87ed57e3bdd51b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864563Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707380}

This change simply avoids using RunUntilIdle. I found that RunUntilIdle was
taking 10 seconds for every invocation -- but not on every test run. I'm not
sure of the cause, but using RunUntilIdle is bad practice anyway.

Where possible, I'm using QuitClosure, but we can't do that in all cases.

Bug: 1014706
Change-Id: Icf538182c9572eaa26aa8d5dd6365981555ee1a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864418
Commit-Queue: Dan H <harringtond@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707379}

This is done to be able to prepare tests before eventually submitting a CL that flips the
experiment to ENABLED_BY_DEFAULT.

Bug: 661143
Change-Id: I6b614bb4400478a7e90de78562a54083af1b3bd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865596
Commit-Queue: Oliver Li <olivierli@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707378}

The ConvertToAXActionData() function in automation_internal_api.cc
was leaving the horizontal_scroll_alignment and vertical_scroll_alignment
fields in AXActionData to their default value of
ax::mojom::ScrollAlignment::kNone.  When the target was a blink object,
web_ax_object.cc would then use 'no scroll' values for both hidden
and partially hidden cases for its converted blink::ScrollAlignment
struct.  This was causing the SCROLLTOMAKEVISIBLE action to not scroll
the view to make the object visible.

Bug: 1015144
Test: Manual test with display assistant screen reader
Change-Id: I20dcd48587704ba42a33c7d27fb81c7d8a8a4ec6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864824Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707377}

https://chromium.googlesource.com/angle/angle.git/+log/299bea643826..7f418fc2677a

git log 299bea643826..7f418fc2677a --date=short --no-merges --format='%ad %ae %s'
2019-10-18 courtneygo@google.com Vulkan: lineloop support for DrawArrayIndirect

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC jmadill@google.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/+/master/autoroll/README.md

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=jmadill@google.com

Bug: None
Change-Id: If1a7fee2a720728e61bc0db22e366d631524546c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869369Reviewed-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@{#707376}

Bug: none
Change-Id: Iadcb1b111922a417e09293e2e73bec7b464e9c13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869031
Commit-Queue: David Benjamin <davidben@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707375}

I guess that this breakage was caused by
https://crrev.com/c/1834142 or related patches.

Change-Id: I1b93bd71743474432de38e86e6384f4b76b575eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869230Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707374}

Before this CL, calling BackForwardCacheImpl::Flush would immediately
destroy all frames in the cache.

If Flush was called during a navigation to a cached page, this could
cause Chrome to crash, as it tried to navigate to a deleted frame.

By calling RenderFrameHostImpl::EvictFromBackForwardCache instead
of directly deleting frames, the above edge case is handled, and
calling Flush at any time becomes safe.

TBR=clamy@chromium.org

Change-Id: I9cb8aa7348868e6bc3089894a7a71cffb7d1fa33
Bug: 1003745
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807321
Commit-Queue: Lowell Manners <lowell@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707373}

Change-Id: I9f45508bb229a809e15423c5d9f48271702719af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866558
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707372}

https://swiftshader.googlesource.com/SwiftShader.git/+log/a68a80a4dbf9..26c6c4a5eb83

git log a68a80a4dbf9..26c6c4a5eb83 --date=short --no-merges --format='%ad %ae %s'
2019-10-18 amaiorano@google.com Fix Win32SurfaceKHR resize issues

Created with:
  gclient setdep -r src/third_party/swiftshader@26c6c4a5eb83

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@google.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/+/master/autoroll/README.md

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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=swiftshader-team+autoroll@google.com

Bug: chromium:b/139372840
Change-Id: If651fc82698b69104e3b02e8aa42de852aba9d0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868508Reviewed-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@{#707371}

This reverts commit f69623b2.

Reason for revert: Unnecessary tests were disabled on unnecessary platforms. Given that the tests are critical to hit testing. Revert this patch for now and disable the one that may actually flake later.

Original change's description:
> [Sheriff] Disable flaky test NestedSurfaceHitTestTest
> 
> SitePerProcessNonIntegerScaleFactorHitTestBrowserTest
> ::NestedSurfaceHitTestTest is flaky.
> 
> TBR=kenrb@chromium.org
> 
> Bug: 1014602
> Change-Id: If7c69bcf4a50c8e7b2646ec8826ea0115018cca6
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862663
> Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
> Reviewed-by: Parastoo Geranmayeh <parastoog@google.com>
> Cr-Commit-Position: refs/heads/master@{#706161}

TBR=parastoog@google.com

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

Bug: 1014602
Change-Id: Ife838c1e96c501d91559051fdcf7cf499bb9090e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869390Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707370}

This feature is not launching in M79.

Temporarily disabled two tricky tests, filed bugs to fix:
http://crbug.com/1015638
http://crbug.com/1015641

Bug: 973481
Test: ash_unittests
Change-Id: I17b2bda3fd383f76dbdf81f86ab638604d923582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865712Reviewed-by: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707369}

Add tests to verify tab sharing UI elements: infobars, contents border
and tab sharing indicator.

Bug: 996722
Change-Id: I5fa5ec7e4a48a66c1ba9b08ff76b84a105961352
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847287Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707368}

https://webrtc.googlesource.com/src.git/+log/c66e004edcf3..55d19e590d9a

git log c66e004edcf3..55d19e590d9a --date=short --no-merges --format='%ad %ae %s'
2019-10-18 gustaf@webrtc.org Add gustaf to audio/OWNERS
2019-10-18 danilchap@webrtc.org Remove redundant fields in PacketBuffer
2019-10-18 sprang@webrtc.org Fix use of unitialized value in test

Created with:
  gclient setdep -r src/third_party/webrtc@55d19e590d9a

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.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/+/master/autoroll/README.md

TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:None,chromium:1015256
Change-Id: I6034e4a4232abb6442dd912bac5f7e99716183e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868974Reviewed-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@{#707367}

The main gist is that timing and animation should be essentially
independent - i.e the former only feeds into the latter by means of the
progress state. Based on this we can perform some cleanups:

 * Any change to the animation target will also invalidate the
   animation parameter state via WillChangeAnimationTarget(), so any
   such change (SetTargetElement, SetAttributeType and SetAttributeName)
   needn't be followed by a call to AnimationAttributeChanged(), so
   remove those.

 * Any change to timing state (such as 'dur', 'repeatDur',
   'repeatCount', 'min', 'max', 'begin' and 'end') will only influence
   the timing and not animation state, so we can drop calls to
   AnimationAttributeChanged() in those cases as well.

 * Since changing animation state should not affect timing, drop the
   call to SetInactive() from AnimationAttributeChanged() - this will be
   handled by timing updates when needed. This also means that
   SetInactive() is no longer used so it can be removed.

After the above changes AnimationAttributeChanged() no longer needs to
be virtual, and can reside in SVGAnimationElement alone.
Also fold InvalidatedValuesCache() into AnimationAttributeChanged()
since it is the only caller.
Take this opportunity to move some state updates from the
SvgAttributeChanged() override (which is for attributes which have an
SVG DOM representation - and 'href' attributes because of how the
dependency notifications work) to ParseAttribute().

Bug: 998526
Change-Id: Id50407cb5fb59601fea573e5963a7d4e1158a317
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869210Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#707366}

Before this patch, in order to support finalization of classes in a
hierarchy, the base class must have had a destructor declared as virtual.
This hurt sweeping time as the sweeper had to execute finalizers for
classes that didn't really have any finalization logic. The patch adds
support for non-virtual destructors in Oilpan that provides the basis
for reduction of finalizers in the followup CLs.

In the backend the logic remained the same for classes that have either
 - virtual Base::~Base or
 - trivial Base::~Base and trivial Derived::~Derived or
 - Base::FinalizeGarbageCollectedObject.
The new logic is:
 - if all of the conditions above don't satisfy, separate GCInfo entries
   will be created for Derived classes.

Bug: 1015427

Change-Id: I99481f0508d99668558283417a15cdf0bfe1ae6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866712
Commit-Queue: Anton Bikineev <bikineev@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707365}

The main frame RenderWidget has page scale and pinch zoom determined
in the renderer by blink. Only child frames hear about it through
the VisualProperties waterfall propagation down the RenderWidget tree.

So stop explicitly sending (default) values to the main frame
RenderWidget (which it will not use) from RenderWidgetHostImpl.

R=avi@chromium.org, wjmaclean@chromium.org

Bug: 419087
Change-Id: I78a03df4d82cd1bb3765db8dffd92ea0e8bed812
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865530
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707364}

This is ground work for having ProfileSyncService's backend task runner use the
ThreadPool.

This class in particular affects LocalSynctTest.Shouldstart when work is done
fully on the Threadpool.

Bug: 1014464
Change-Id: Id91c6b1682648a6fdb38efef5145ab4d6af0b2e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865427
Commit-Queue: Oliver Li <olivierli@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707363}

The test DetachToBrowserTabDragControllerTest no longer
relies on extensions to launch a web app.

Bug: 1865741
Change-Id: Iee6850e33c06639e6b6bf4efa533c3cba85c4df3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866223
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707362}

Bug: none
Change-Id: I8c605899ca10c4482390f8250bc79de35501fc4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869224
Auto-Submit: Marc Treib <treib@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707361}

The not-site-per-process isolated-code-cache web tests currently assume
that cross-origin resources are cached when code cache site isolation is
not active. This causes them to fail when the HTTP Cache is partitioned
by Network Isolation Key. We thus disable the partitioned HTTP Cache for
those tests and add a new test for when site isolation is not active,
but the HTTP Cache is still partitioned.

Bug: 1009628
Change-Id: I0d5d438d9564d3f659b93484a5bcc8aa56d2cd26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865421Reviewed-by: Shivani Sharma <shivanisha@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Alex Turner <alexmt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707360}

Bug: 1015447
Change-Id: I252d93ab9269b83402300d9835797d5399a40a19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868995Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#707359}