GitLab

This is a more suitable name for this class as it will be used
to track dedicated workers and shared workers in the future.

Bug: 1041093
Change-Id: I711aff37886fa63ad8b799694b9ab81f8bcf3d10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993728
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734684}

AppListItemView ctor was calling SetBackgroundBlurEnabled, which depends
on icon_, before the icon view was actually added as the item view child
(and thus before icon_ ptr was set).

BUG=1043908

Change-Id: I9e5b52c8030899a991e08a462f511bff3292e886
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2018123Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734683}

This is a speculative fix. As per comment #5 on that bug, we are
probably obtaining a WeakPtr from an invalid raw ptr.

Bug: 1038776
Change-Id: I0c2a819d53cd83df1e2042cafb3f7fc94bd681b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016344
Commit-Queue: Jonathan Backer <backer@chromium.org>
Reviewed-by: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734682}

Adds a new option for users in non-managed accounts to clear synced
data from their local device when signing out.

Bug: 1005509
Change-Id: Iae3b599b3ca3698b2a176bd56b470c6787c74367
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007695
Commit-Queue: Nohemi Fernandez <fernandex@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734681}

This should be practically a no-op change since we specify *_ld
explicitly in both the ebuild and in Simple Chrome (for now). But
it will make `gn args --list` print more accurate info wrt these args.

Bug: 937821
Change-Id: I155fd8e2fd6a6275522c768ea96c78eb397a7a7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014127Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734680}

The zero-crossing frequency estimation is very sensitive to the concealment
mechanism in WebRTC. By experimentation this seems to happen
more often in the initial transition of the stream. Skip the
first 200 ms in the verification to make the frequency estimation
more robust.

Restore frequency estimation error limit to +/- 50 Hz.

Bug: none
Change-Id: I8a7169cc20047395cb0c566d98f9d780b73f63d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014906
Commit-Queue: Johannes Kron <kron@chromium.org>
Auto-Submit: Johannes Kron <kron@chromium.org>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734679}

conformance/textures/misc/canvas-teximage-after-multiple-drawimages.html

Observed failing on Win Vulkan NVIDIA Passthrough,
but skipping on all Win Vulkan Passthrough as ANGLE doesn't actively
support Win Vulkan Passthrough at the moment.

Bug: angleproject:4334
Change-Id: If8add00e24ec6fdaeaeeb5e4626ffb7de86c483d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017903Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Auto-Submit: Shahbaz Youssefi <syoussefi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734678}

Context: Android Browser Test has no way to control the Web Contents of
Payment Handler. However, the control is needed, in order to make it
easier to cover Payment App behaviours.

Before change:
Android Browsertest could not run script in the WebContents of Payment
Handler, because the test has no access to the WebContents.

After change:
Android Browsertest could run script in the WebContents of Payment
Handler.

Change:
* Build the plumbs for Android Browser Tests to get the
WebContents from ExpandablePaymentHandler UI.
* Added a test to cover the Payment cancel flow.

Bug: 1042892

Change-Id: I3b8813eed4c3bd05658aae465b888410954c1fd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013810
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734677}

This patch implements the serializer function for skottie draw ops. It
utilizes the transfer cache to avoid moving the entire skottie byte
data across IPC for every frame update.

This functionality is not included in android since android will not be
using it.

To achieve this the following modifications were also
made to the SkottieWrapper class:
  - A unique id is generated using fast hash for a given animation
    byte data.
  - Store the raw byte data in the object.
  - Modify the constructor to differentiate between serializable &
    non-serializable constructors.

Test=Added unit tests for transfer cache and paint op buffer.

Bug: 894635
Change-Id: I9fb7b5e7f761a84e6b6112d6e73e5681e9d86342
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003809
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734676}

SnapCoordinator needs to update all its scroll containers data if one of
them asks for an update until the update is completed. i.e. this state
should not be reset by any of its scroll containers.

This bug is not exposed because a scroll container only sets the state
to false during SnapCoordinator updates all its containers.

This patch also updates the name to reduce ambiguity.

Bug: None
Change-Id: Ibbb2eccc5a9f1b36f5fc1db5bc949ded878a1d0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014980
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734675}

A website can check if its own WebAPK is installed by using the platform
value `webapp` and setting url to the Web App Manifest's url.

Bug: 1043970
Change-Id: I73853eb4b9ac63b1a918661ca51206611ac666e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013103Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734674}

We expect SyncMetadataResponse.hasEncryptedGroupPrivateKey() to be true
if and only if there was a non-empty group private key for CryptAuth to
send. However, this CL guards against an empty group private key string.

See also http://b/145600035.

Bug: 951969
Change-Id: I4bac0f8cbc3ef4c4b55ea7195a08fea28fd52250
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003799
Auto-Submit: Josh Nohle <nohle@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734673}

This CL defines two new metrics (Activated/Cancelled) for gesture navigation.
They will be used in M81 to measure the cancellation rate.
The old metrics (Triggered/SwipedOverThreshold) that gave too optimistic
results will be left unused.

Bug: 1013405
Change-Id: Ie4e4ef85244412af52409f6b255440a295ffd391
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014202Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734672}

Bug: 1015136
Change-Id: I2bef165b3fedd21d4a04340a89de6cd235469e02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1951970
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734671}

If a channel sends a message to what turns out to be a dead-name port,
before the channel processes the kernel's dead-name notification, the
channel would leak the dead-name right. This is because the dead-name
notification message contains a port right that must be destroyed, and
that right is not transferred as a normal message descriptor. Therefore,
the right is not automatically released when the message remains in the
kernel message queue and the associated receive right is destroyed.

To fix this, if a channel fails to send a message because it is to an
invalid destination (namely, a dead-name), do not immediately report the
error. Instead, wait for the channel to process the dead-name
notification so that the port right can be appropriately disposed.

Bug: 1041682
Change-Id: I99ffdea096670ef1e133f62ae269292b1d7e290a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013524Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734670}

The ChromeBrowserState has been moved from the "ios" namespace
to the global namespace by http://crrev.com/c/2014913. Fix the
uses from ios::ChromeBrowserState to ChromeBrowserState.

Also remove includes of chrome_browser_state_forward.h and use
a simple forward declaration instead (since the old name is no
longer necessary).

This CL was uploaded by git cl split.

R=michaeldo@chromium.org

Bug: 1042208
Change-Id: I76fab1199331f19d4fda31396e4631a16e2c9242
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017343
Auto-Submit: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734669}

Screen readers read from the top of the page on a scroll to text
navigation, instead of the targeted text. This patch adds an AX call
that is made when navigating to an anchor, as is done with element
fragment anchors.

Confirmed this works with TalkBack on Android.

Bug: 1044644
Change-Id: If5c905b083189efd7276f64abc4a547f81f6b054
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015132Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734668}

The ChromeBrowserState has been moved from the "ios" namespace
to the global namespace by http://crrev.com/c/2014913. Fix the
uses from ios::ChromeBrowserState to ChromeBrowserState.

Also remove includes of chrome_browser_state_forward.h and use
a simple forward declaration instead (since the old name is no
longer necessary).

This CL was uploaded by git cl split.

R=jlebel@chromium.org

Bug: 1042208
Change-Id: I567615141ce700cd3edc6327de23b331f38c69a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017468
Auto-Submit: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734667}

BUG=1044828

Change-Id: I74cf58b4669851006d97f1b81c7a0f5ea6d3e609
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016964
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Avi Drissman <avi@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734666}

BUG=1044828

Change-Id: I375866984e4878833b19c29a1276af948756b228
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016860
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Avi Drissman <avi@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734665}

- Consolidate Pepper code within a BUILDFLAG(ENABLE_PLUGINS) section
  in browser_prefs.cc.
- Make AddStringsForPdf() a no-op if BUILDFLAG(ENABLE_PDF) is not set in
  resources_private_api.cc.

Bug: 1027360
Change-Id: Ie99dcc278d3b30282f4215e36ac95a6434fa0ebf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017663Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734664}

This is a reland of ae629163

Original change's description:
> viz: Fix FindLatestSurfaceUpTo when there is conflict
>
> The condition used in the binary search was wrong. Fixed it and added
> a unit test.
>
> Bug: 1000868
> Change-Id: Iaf4af1bdfdb88db1082bfae89a3783faed860934
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800743
> Auto-Submit: Saman Sami <samans@chromium.org>
> Commit-Queue: Jonathan Ross <jonross@chromium.org>
> Reviewed-by: Jonathan Ross <jonross@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#696170}

TBR=jonross@chromium.org,samans@chromium.org

Bug: 1000868, 1015120
Change-Id: I2b793035cd689551217e23de5e43d0fd855cbf37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017945Reviewed-by: Nick Burris <nburris@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734663}

This metric records the time between a password reuse dialog is shown
and a user clicks one of the buttons on the dialog. It will help us
understand if users pay less attention to dialogs on Android than on
desktop.

Bug: 1036042
Change-Id: I2f525778d3b2109b05105f5456e5bc16ddc94f39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013493
Commit-Queue: Xinghui Lu <xinghuilu@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Bettina Dea <bdea@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734662}

- journal contains system-wide logs (in a machine-readable format).
- power_manager contains logs from the daemon that controls system
  power, and may provide some insight when a device/VM shuts down
  unexpectedly

Bug: 1043953
Change-Id: I14721bdbdc62095d864145bd3d491c2d880b1df2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016665Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734661}

It was never used and never will be as the IO thread is being
phased out altogether.

This is a partial revert of https://chromium-review.googlesource.com/c/chromium/src/+/1660340

This CL keeps (diff with the raw revert on PS1):
 1) TaskQueueThrottler's Metadata inner class which isolates some logic
 2) TaskObserver::OnQueueNextWakeUpChanged dropping the unused TaskQueue* param
 3) TaskQueueImpl::SetObserver in favor of TaskQueueImpl::SetOnNextWakeUpChangedCallback
   (more adaptable to future instrumentation)
 4) BrowserTaskQueues::Handle as a ref-counted class
   (could go back to being copied around but avoiding duplicate state
    makes state management easier and even essential in some cases like
    validator_sets_ used to require)
   Note: The provider of Handle at the time has been renamed from
         BrowserIOTaskEnvironment to BrowserIOThreadDelegate if you're
         looking for it.
   Side-effect: this keeps all the . to -> usage changes for Handle.

And removes:
 A) TaskQueueObserver::OnPostTask
 B) BrowserTaskQueues::Validator
 C) ScopedDoNotUseUIDefaultQueueFromIO

This is associated to crbug.com/1026641 because supporting
BrowserTaskQueues::Validator adds an unnecessary burden (not that it'd
be impossible to re-add them if explicitly necessary post-migration).

TBR=nasko@chromium.org (BUILD.gn)

Bug: 863341, 1026641
Change-Id: I7bfdc8730cacbac33e2e9b57d1936b6755033753
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008462
Commit-Queue: Gabriel Charette <gab@chromium.org>
Auto-Submit: Gabriel Charette <gab@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734660}

Now hotseat is hidden after restoring the active window from overview.
The reason is illustrated in the bug description.

Actually the in-app shelf only exists in tablet mode where no mouse
is available (if there is the mouse connected, device will switch to
clamshell mode). So there is no point to check whether mouse event
is enabled for shelf widget in this scenario. So skip that code block
in tablet mode. Meanwhile, the CL uses the additional attribute to
ensure that hotseat is not hidden by window restoration.

Bug: 1044366
Change-Id: I6cd2568f2eb7a32aabb8a6be373118ec6c501634
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015802Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Andrew Xu <andrewxu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734659}

 - Add polymer_modulizer() and js_modulizer() rules as necessary to
   generate a Polymer3 version of certificate-manager at build time.
 - Remove unnecessary settings.Router references from tests.
 - Auto-generate tests for the Polymer3 version (and update Settings
   WebUI data source as needed)
 - Add a missing assertion in js_modulizer.py that was discovered.

The Polymer3 version will be used by follow up CLs to migrate
chrome://certificate-manager and eventually chrome://settings

Bug: 1042558
Change-Id: I3a857a45d8f6db578f2059a619720d78fd863e8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006615
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734658}

The test conformance2/rendering/framebuffer-texture-level1.html is flaky
on AMD GPUs on Mac Retina:

https://ci.chromium.org/p/chromium/builders/try/mac-angle-rel/4837
https://ci.chromium.org/p/chromium/builders/try/mac-angle-rel/4791

This CL will suppress that test while the issue is investigated.

Bug: 1044638
Change-Id: Iac30d591a1126d8cbdc373167ce3591b6279b210
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015440
Auto-Submit: Tim Van Patten <timvp@google.com>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734657}

There is logic in GLOutputSurface to ensure that SetDrawRectangle() is
only called once per swap. However, it's possible for
Display::DrawAndSwap() to to draw and not swap. GLOutputSurface will
ignore the first SetDrawRectangle() after Reshape() if the last swap was
skipped.

DirectCompositionChildSurfaceWin::Resize() releases the draw texture, so
it should be safe to call call SetDrawRectangle() again after Reshape()
even if SwapBuffer() wasn't called.

This CL also implements equivalent logic in SkiaOutputSurfaceImpl for
SkiaRenderer.

Bug: 1042007
Change-Id: Ib1a8f5092d004172d37fe4c16d8a7144cbc7ce8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013346Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734656}

This reverts commit 9189f6dd.

Reason for revert: This CL is unrelated to the test that is was suspected of making flaky.

Original change's description:
> Revert "Exo: Undo conflation of relative-pointer and pointer-constraints"
> 
> This reverts commit 01116522.
> 
> Reason for revert: suspected of causing
> PointerLockBrowserTestWithOptions.UnadjustedMovement to be flaky
> 
> See bug: 1043985
> 
> Original change's description:
> > Exo: Undo conflation of relative-pointer and pointer-constraints
> > 
> > When it was first implemented, adding a relative-pointer-delegate would
> > also enable pointer capture (locking the pointer).
> > 
> > This change makes it so that the pointer can only be locked through the
> > pointer-constraints protocol.
> > 
> > Bug: b/124059008
> > Test: exo_unittests, manual testting using ArcPointerCaptureTestApp
> > Change-Id: Ied0f1c658aa713026e622f4ce26009e261d4f653
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992355
> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> > Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org>
> > Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#733497}
> 
> TBR=mukai@chromium.org,oshima@chromium.org,prabirmsp@chromium.org
> 
> Change-Id: I8581f298f099cb7a9a006a1b578f6345184da1d3
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: b/124059008
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012517
> Reviewed-by: Nina Satragno <nsatragno@chromium.org>
> Commit-Queue: Nina Satragno <nsatragno@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#733612}

TBR=mukai@chromium.org,oshima@chromium.org,nsatragno@chromium.org,prabirmsp@chromium.org

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

Bug: b/124059008
Change-Id: I5e0c6615b9dce0c48f94d6b227763cfc205954b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015301Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Nina Satragno <nsatragno@chromium.org>
Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org>
Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734655}

https://swiftshader.googlesource.com/SwiftShader.git/+log/cb4d2c38a343..5ef91b82cbed

git log cb4d2c38a343..5ef91b82cbed --date=short --first-parent --format='%ad %ae %s'
2020-01-23 amaiorano@google.com Subzero: temp fix Float4 % Float4 (FRem)
2020-01-23 capn@google.com Use UNIMPLEMENTED() for missing functionality we claim support for
2020-01-23 capn@google.com Replace all UNIMPLEMENTED() with UNSUPPORTED()

Created with:
  gclient setdep -r src/third_party/swiftshader@5ef91b82cbed

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
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: I70a9f967fd60cb48886ea743cc82f5bb868db877
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016288Reviewed-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@{#734654}

Strips the stack_unwinder module interfaces and contents down to the
minimal Java required to get the dynamic feature module to work from
native code. The module will be providing native code interfaces[1],
which will be consumed by native code, so it doesn't make sense to
interpose more Java than necessary in between. It's also the case that
the parts of the DFM Java API that deal with the Play Store can't be
used within the sandboxed renderer process.

This change exposes via JNI the StackUnwinderModuleProvider's functions
to query and request installation. This is the only Java-provided
functionality that will be required for manipulating the module from
native code.

1. Design doc: https://docs.google.com/document/d/1QB5IzWuVKfoPdPuiyRok2MUEta1FmRLIQkq1wDATA4k

Bug: 1027654
Change-Id: Ie69e687335a753c17206fc6c81ae981118c698b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003298Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Fred Mello <fredmello@chromium.org>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734653}

Since the CheckClientDownloadRequest will no longer be run on deep
scanning, we need to check the file size and encryption within the
DeepScanningRequest. This CL moves that functionality.

Bug: 1041578, 1020215
Change-Id: If134cfb8097b666cdf5f9057e2921f5634bcbf22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007972Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734652}

Bug: 1043481

TBR=bashi@chromium.org

Change-Id: Id5c998c8fc81c98fd5ff898d1b953aeddadba19c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016351Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734651}

Current theory is that JS channels can be set before the frame finishes
its initialization, and V8 context creation can occur on the Install()
path, this violates some assumptions and crashes. So delay any Install()
calls until after the main world context has been created.

Bug: b/148202893
Test: no crashes seen on device
Change-Id: I55255d9afed36a6e4c97dff8bfbea3c20a4a856a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016350
Commit-Queue: Albert Chaulk <achaulk@chromium.org>
Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734650}

https://webrtc.googlesource.com/src.git/+log/48655cfdbfd9..40899b279798

git log 48655cfdbfd9..40899b279798 --date=short --first-parent --format='%ad %ae %s'
2020-01-23 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 487ee81f..c0451968 (734357:734489)
2020-01-23 minyue@webrtc.org Revert "Send absolute capture time through audio coding module."

Created with:
  gclient setdep -r src/third_party/webrtc@40899b279798

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

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: If5c7f63ed8ff5356665d49cc87a624062b305523
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017649Reviewed-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@{#734649}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/1b20535e..fde258b4

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I4c9225e9bf101b423747dc158fdd715e8cf78342
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017105Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#734648}

SplitSettingsSync will allow the user to opt-out of browser sync.
However, IdentityManager::GetPrimaryAccount() assumes the user has
consented to sync. Switch to using the "unconsented" primary account,
which exists whether or not the user has consented to sync.

This code doesn't add a DCHECK that the unconsented primary account
exists because there are managed guest session tests that don't
have a primary account but still exercise this code path.

      and on device

Test: existing login browser tests, manual tests of login on linux
Bug: 1042400
Change-Id: I14ee7bcc18c294dee31c26fcc9bed537836516b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015589
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734647}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/e504fd6a5f25..cd43517dce3c

git log e504fd6a5f25..cd43517dce3c --date=short --first-parent --format='%ad %ae %s'
2020-01-23 mandy.chen@microsoft.com Roll protocol changes

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@cd43517dce3c

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/+/master/autoroll/README.md

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

Change metal_util::TestShader to test either compile or link, and
change the default behavior to link.

Add inline data for a trivial test shader. Add code to modify the
bitcode, to defeat caching.

Ensure that the Metal calls for the test are invoked on a thread
that has base::TaskPriority::HIGHEST.

TBR=jvanverth

Bug: 974219
Change-Id: I35e688c3758af2e03f893a1ccbef7aef6b778b23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015486Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734645}