GitLab

This is a step toward supporting chrome browser windows under
single-process and multi-process mash.

Break AXHostService into two parts. The core AXHostService manages
a map of AXRemoteHostDelegates. Each AXRemoteHostDelegate is-a
ui::AXHostDelegate and therefore can handle PerformAction requests
from accessibility extensions. AXHostService receives incoming
AXEvents from remote apps and routes them to the correct
AXRemoteHostDelegate, which forwards them to the extension.

Integration tests already exist in SpokenFeedbackTest.

Added unit tests.

Bug: 888147
Test: unit_tests, views_mus_unittests
Change-Id: If2ee438b310acba9437a251bd77e06bfb7d9a099
Reviewed-on: https://chromium-review.googlesource.com/c/1260205
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596906}

This reverts commit 7cff6f2f.

Reason for revert: NavigationPopupTest.testFaviconFetching started crashing after this landed in https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20CFI/3164

Original change's description:
> Refactor NavigationPopup to not expose the View type to clients.
> 
> This is a step towards removing ListPopupWindow and using a vanilla
> Popup to deal with styling issues.
> 
> BUG=800033
> 
> Change-Id: I79506cdd7c3e840e13e9ebbabce39948a9fa5936
> Reviewed-on: https://chromium-review.googlesource.com/c/1259480
> Commit-Queue: Ted Choc <tedchoc@chromium.org>
> Reviewed-by: Becky Zhou <huayinz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#596734}

TBR=tedchoc@chromium.org,huayinz@chromium.org

Change-Id: I6a7d3c914fcca88e64eea4158fbea9db224d762c
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 800033
Reviewed-on: https://chromium-review.googlesource.com/c/1263344Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596905}

As requested by UI review.

Bug: 891379
Change-Id: I0f5d69300852a4a8cae191684ceddb2c5fbfaa15
Reviewed-on: https://chromium-review.googlesource.com/c/1262431Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596904}

This CL adds several UMAs to track time spend each stage of service
worker involved main resource loading. The purpose of these UMAs is
to make it easier to investigate performance bottleneck.

Design doc:
https://docs.google.com/document/d/16K2X5k6hUq7lZSee-KXR9FUeSTEEypDXCjYbu_CvkT0/edit?usp=sharing

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Bug: 877972
Change-Id: Ibb2433cafb090e66b450236ef2f5f1f4baa918bf
Reviewed-on: https://chromium-review.googlesource.com/c/1256384Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596903}

When the presentation request is set, use its origin in the dialog
header. E.g. "Cast youtube.com" instead of "Cast".

If the user selects a non-tab source (desktop or local file), switch to
using just "Cast".

Bug: 851610
Change-Id: I7c672e458fa82af0182e1d9ed20a7f922e3ad814
Reviewed-on: https://chromium-review.googlesource.com/c/1259618
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596902}

This CL adds a 4dp vertical margin on either side of the list inside a
Dropdown window. This is needed for the Autofill refresh.

Bug: 874077
Change-Id: If37016cafe886417cd4a82e9b59f75dd8ccbba7d
Reviewed-on: https://chromium-review.googlesource.com/c/1262962
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596901}

https://webrtc.googlesource.com/src.git/+log/f638bbc181eb..264079a57aec


git log f638bbc181eb..264079a57aec --date=short --no-merges --format='%ad %ae %s'
2018-10-04 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 70554c25..c5c13a1e (596607:596716)


Created with:
  gclient setdep -r src/third_party/webrtc@264079a57aec

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Idab1cc9860710c239fd9be8515a4421b28d54d6e
Reviewed-on: https://chromium-review.googlesource.com/c/1262855Reviewed-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@{#596900}

The Feed NTP attaches the SnapScrollHelper before scroll position
restoration, but legacy Zine attaches after. Thus, changing the current
logic for search box scrolling to handle scroll position restoration
well.

Bug: 889228
Change-Id: Ib2055b0e98b877ee3ced35356af2cf3b26743480
Reviewed-on: https://chromium-review.googlesource.com/c/1259609
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596899}

This CL adds a few new .h and .cc files for upcoming omnibox Pedals
prototype.  None of this code is used yet, but changes necessary
to ensure that one Pedal can be used are included so it compiles.

Change-Id: If3d03e1fd532fdace55bde941ab1d5597748a168
Reviewed-on: https://chromium-review.googlesource.com/c/1247223
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596898}

If browser is not started, we don't have a profile to get the tracker
The Download completed message is used by in-product help/

BUG=842245

Change-Id: I2716dbc659e7e192198070ccd9e3d700a89f2810
Reviewed-on: https://chromium-review.googlesource.com/c/1263275Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596897}

Original CL:

- https://codereview.chromium.org/14769008

  Fix mmap region iteration while no regions are recorded.

  If no mmap regions are recorded, iteration failed since the RegionSet
  (std::set) object is not initialized.

  BUG=162208
  R=willchan@chromium.org

  Committed:
  https://src.chromium.org/viewvc/chrome?view=rev&revision=198878

BUG=724399,b:70905156

Change-Id: I9659e486e5be89e6c36bcdf83d794dee3295e91b
Reviewed-on: https://chromium-review.googlesource.com/c/1130807Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596896}

We now test for existence of the path /dev/kvm at startup. This
directory only exists for board which can run VMs. As a side effect, this will address the attached bug.

Bug: 891554
Change-Id: Icd24f6da9f3490e54b9d86bbefa7a1350627d9c0
Reviewed-on: https://chromium-review.googlesource.com/c/1261840
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596895}

This reverts commit bebc3d33.

Reason for revert: Causes namespace issues with ontherecord download content ids.

Original change's description:
> Download shelf : Fix for incognito
> 
> Currently incognito downloads are showing up on the download shelf for
> normal profile.We need to initialize the DownloadManagerDelegate and
> DownloadShelfController for incognito.  Also we need to filter out the
> updates for the right profile in the controller since aggregator sends
> updates for all profiles.
> 
> Bug: 881499
> Change-Id: I309d1673e87de44b870d4efaca606390dd46345e
> Reviewed-on: https://chromium-review.googlesource.com/c/1257003
> Reviewed-by: Min Qin <qinmin@chromium.org>
> Reviewed-by: Rayan Kanso <rayankans@chromium.org>
> Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#596735}

TBR=dtrainor@chromium.org,qinmin@chromium.org,shaktisahu@chromium.org,rayankans@chromium.org

Change-Id: I996da981cb9ccf586a1c6965e65c2a90b687b296
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 881499
Reviewed-on: https://chromium-review.googlesource.com/c/1263339Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596894}

When a user presses a mouse button over a PDF, the PDF receives all
mouse input until there is a corresponding MouseUp. This is currently
broken for OOPIFs because the browser process doesn't know when a PDF
is supposed to capture input and so it doesn't always route events to
the right process. This change causes renderers to signal the browser
process for mouse capture when a PDF is is clicked.

Bug: 864957
Change-Id: If17587d5ca475d9a8ac03a3bba301d4084e6d4e3
Reviewed-on: https://chromium-review.googlesource.com/c/1203883
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596893}

Change-Id: Ieb633af2954b9352f4650e3ba773369cbd530a32
Reviewed-on: https://chromium-review.googlesource.com/c/1260216Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596892}

Bug: 854101
TBR: alemate@chromium.org
Change-Id: If980f6b3e45fd7f35378e197a2781d9ce033b28c
Reviewed-on: https://chromium-review.googlesource.com/c/1251536
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596891}

Shared worker's factory bundle's default factory can now be AppCache
rather than network, since support for shared worker + AppCache was
added in issue 715632.

Use CloneWithoutDefaultFactory() to make the service worker fallback
factory accordingly, as is done for frames in
RenderFrameImpl::BuildServiceWorkerNetworkProviderForNavigation and
dedicated workers in RenderFrameImpl::CreateWorkerFetchContext.

No test added since we don't have a feature that can be set as the
default factory and be used in conjunction with service worker. The
point of the change is to fix the comments and make it consistent with
the other callsites.

Bug: 715632
Change-Id: Ie1ee1cae5423fd81933dea599e6d724a12bf51f7
Reviewed-on: https://chromium-review.googlesource.com/c/1260883Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596890}

This CL changes how the drawable for the refresh button in the app menu
is tinted. Now Drawable object is tinted instead of relying on
ImageButton tinting, because ImageView can't tint LevelListDrawable on
some Android versions.

Bug: 891593
Change-Id: Ic5d45b3f281f3a1dc44cada814e5c0d83b14b2b4
Reviewed-on: https://chromium-review.googlesource.com/c/1262636Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596889}

Each action in the Captured Sites Automation Framework has a target
frame. The framework uses the IFrameWaiter object to acquire a handle to the RenderFrameHost of
the target frame. A target iframe can be identified by its name, its URL
or the origin of its URL.

Currently the IFrameWaiter object scans for potential targets everytime
Chrome adds a new frame. This change adds 2 additional hooks to
IFrameWaiter to scan for potential targets:

1. When a frame changes its name.
2. When a frame finishes loading a new URL.

Bug: 847905
Change-Id: Ie2b8c2f19a9f08696d474aff6af019ae116b513c
Reviewed-on: https://chromium-review.googlesource.com/c/1260510
Commit-Queue: Yiming Zhou <uwyiming@google.com>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596888}

TBR=smut

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ib20eeebffce6a7c4a51534bafd33e13d7d0a228f
Reviewed-on: https://chromium-review.googlesource.com/c/1262757
Commit-Queue: iOS Autoroller <ios-autoroller@chromium.org>
Reviewed-by: iOS Autoroller <ios-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596887}

Added per-project functions for credit card uploads. Each project
has its own requirements/parameters, so it must have its own
function to determine its key. Each project also has its own
private function to return a project prefix string.

Bug: 884717
Change-Id: Ib241378a8fa6a99071898f61425cdcefe69a16a0
Reviewed-on: https://chromium-review.googlesource.com/c/1260502Reviewed-by: Jared Saul <jsaul@google.com>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Anne Lim <annelim@google.com>
Cr-Commit-Position: refs/heads/master@{#596886}

https://chromium.googlesource.com/catapult.git/+log/1b6e81b579f3..3f7d74f7cd02


git log 1b6e81b579f3..3f7d74f7cd02 --date=short --no-merges --format='%ad %ae %s'
2018-10-04 simonhatch@chromium.org Dashboard - Remove old buildbot link if new one is there
2018-10-04 sebmarchand@chromium.org Add more system stats to the UI tracing view


Created with:
  gclient setdep -r src/third_party/catapult@3f7d74f7cd02

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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

BUG=chromium:884961
TBR=sullivan@chromium.org

Change-Id: I943091e568645704071b431cb1da5c0aa2f29693
Reviewed-on: https://chromium-review.googlesource.com/c/1262240Reviewed-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@{#596885}

This reverts commit e5d0061d.

Reason for revert: only switch after confirming WAI

Original change's description:
> Make WebKit Win10 part of win-ci.
> 
> BUG=790343
> 
> Change-Id: I64d509837aaf84043e1e3e749bcda748e0c42da4
> Reviewed-on: https://chromium-review.googlesource.com/c/1260012
> Reviewed-by: Ryan Tseng <hinoka@chromium.org>
> Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#596409}

TBR=hinoka@chromium.org,jchinlee@chromium.org

Change-Id: I0f3c5228ab4fe404c31244bbcf92f9328ac3b9f1
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 790343
Reviewed-on: https://chromium-review.googlesource.com/c/1263051Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org>
Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596884}

Referrer chains are broken in M69 if the page sets window.location. This
was already fixed at HEAD, so this CL simply introduces a browser test
to prevent regression.

Change-Id: I4d29b3a4ae36b931273125191f6aa3fe703b44c6
Reviewed-on: https://chromium-review.googlesource.com/c/1262966Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596883}

This change extracts an abstract base class called FidoDiscoveryBase
from FidoDiscovery. The FidoDiscovery::Observer interface is moved into
the base class, and its signature is changed to allow observing the
instantiation and destruction of FidoAuthenticator instances rather than
FidoDevice. I.e. FidoDiscovery::Observer::Device{Added,Removed} becomes
FidoDiscoveryBase::Observer::Authenticator{Added,Removed}.

FidoDiscovery takes on the responsibility of instantiating and owning
FidoAuthenticator instances (more specifically, FidoDeviceAuthenticator
instances). The AuthenticatorMap in FidoRequestHandlerBase now only
holds plain FidoAuthenticator pointers, rather than owning the
unique_ptrs.

This gets us closer to getting platform-y authenticators (Touch ID,
Windows) injected via Discovery implementations, rather than
implementing custom interaction between FidoRequestHandlerBase and
AuthenticatorImpl for them (see
SetPlatformAuthenticatorOrMarkUnavailable).

Better naming might have been "FidoDeviceDiscovery" for FidoDiscovery
and perhaps "FidoDiscovery" for FidoDiscoveryBase, but that would be a
rather large diff.

A sensible additional refactoring might be to make
FidoDeviceAuthenticator own its associated FidoDevice.

Change-Id: I05d9c24819745c784fef3898bec8d6bb63d2f503
Reviewed-on: https://chromium-review.googlesource.com/c/1256016
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Jun Choi <hongjunchoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596882}

This makes Slides read more smoothly, but will not differentiate
between spaces between words and paragraphs in intonation.

DOM ordering is used rather than visual ordering, this is unchanged.

Bug: 809734
Change-Id: Ieb17eef53f4de360f2d1f13e8a561d3aa05af115
Reviewed-on: https://chromium-review.googlesource.com/c/1262086Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596881}

Also adds a "Settings" link on Android only that opens the
Data Saver settings menu, and related UMA.

Bug: 889124
Change-Id: I087a4719671d5ce811c52331f2906e1e4202ced4
Reviewed-on: https://chromium-review.googlesource.com/c/1258972Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596880}

NavigationPredictor: Normnalize the final anchor element
prediction score to between 0.0 and 100.0. This makes it easier
for different experiment arms to change the scales of different
anchor element properties and still compare the final
anchor element score.

Bug: 891736
Change-Id: I7378fe3d8fe68cde32c6216802b077432758562a
Reviewed-on: https://chromium-review.googlesource.com/c/1259142
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596879}

Android WebView limits cache to 20MiB as of now, which resulted, before
this change, in a 2.5MiB size limit for individual resources... resulting in
parallel fetches to those resource failing due to lack of a cache entry to
back multiple readers.

This bumps the limit to at least 5MiB to mitigate somewhat.

Bug: 890973
Change-Id: Ic6b587414c85d47dbc62411d508446e33cb5cd17
Reviewed-on: https://chromium-review.googlesource.com/c/1262575Reviewed-by: Asanka Herath <asanka@chromium.org>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596878}

https://pdfium.googlesource.com/pdfium.git/+log/38772e9f7456..d8ac668fad02


git log 38772e9f7456..d8ac668fad02 --date=short --no-merges --format='%ad %ae %s'
2018-10-04 tsepez@chromium.org Remove CPWL_Wnd::GetClassName() and overrides.
2018-10-04 tsepez@chromium.org Remove CPWL_EditCtrl::m_pEdit null checks.


Created with:
  gclient setdep -r src/third_party/pdfium@d8ac668fad02

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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.


TBR=dsinclair@chromium.org

Change-Id: I390f8b85edb0e19e2bcf4a7dc18b0a276efe840e
Reviewed-on: https://chromium-review.googlesource.com/c/1262776Reviewed-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@{#596877}

Bug: 117179835
Test: cast_audio_backend_unittests, tuning tool
Change-Id: I57b1a3343c5964b96761eef4e2936da6cf5105c0
Reviewed-on: https://chromium-review.googlesource.com/c/1258314
Commit-Queue: Benjamin Shaya <bshaya@chromium.org>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596876}

This is not used in production as the linux ImageTransportSurface
strictly perfers the surfaceless version. It also never quite worked
correctly as we can't emulate the EGL default framebuffer fully on top of
surfaceless.

Bug: none
Test: compile

Change-Id: I21a51df5bce5f1a7221611d92b929624fef44a0a

Reviewed-on: https://chromium-review.googlesource.com/c/1262616Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596875}

- Adds support for placeholder text to cr-searchable-drop-down
- Adds example share path \\server\share to File share URL field in the
add share dialog.

Bug: chromium:889287
Change-Id: I0ee1bc39e10acec419e4ec8935e6a45caa790a18
Reviewed-on: https://chromium-review.googlesource.com/c/1258309
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596874}

This is not used with surfaceless; vsync timing information comes via the
PresentationCallback.

Bug: none
Test: compile

Change-Id: I73895bc913dfc2cc03381debcac83108828301d2

Reviewed-on: https://chromium-review.googlesource.com/c/1262615Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596873}

This function has no call sites.

Bug: none
Test: compile

Change-Id: I8865153bb65b430809a5a5e1bbbe540c3c5b816f
Reviewed-on: https://chromium-review.googlesource.com/c/1262434Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596872}

The comment implies it can only be used from tests, which isn't entirely right.

BUG=none
TEST=comment only change

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

Bug: 814405
Change-Id: I55b8c06553a45c24a5527bc5b482d19d9d76fd8f
Reviewed-on: https://chromium-review.googlesource.com/c/1262915Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Andrew Luo <aluo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596870}

In order to better handle messages sent from RenderFrames in
the renderer process during unload event, we should keep
the browser side objects alive as long as possible.

This CL moves ownership of subframes to RenderFrameHost, which
can allow the subframes to live until the unload handler of the
top parent has completed running. The CL is just a mechanical
move of the ownership and does not change the lifetime of
subframes for now, which will come in a follow up CL.

Bug: 609963
Change-Id: I52456dc1bf68cb15caab527c16c96ddd13a80838
Reviewed-on: https://chromium-review.googlesource.com/c/1098562Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596869}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c92be0189275..bf0d2438ae53


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

The AutoRoll server is located here: https://autoroll-internal.skia.org/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.


TBR=mmoss@chromium.org

Change-Id: I2d393e0c019d1100abf565dc5db9fcca0506329a
Reviewed-on: https://chromium-review.googlesource.com/c/1262775Reviewed-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@{#596868}

Requesting new rotation while coyping layer used to cancel
the existing rotation and moved to new one, which was causing
an issue in Android CTS. Instead, apply the requested orientation
immediately and move to next rotation.

This still skips the pending request if yet another request is made
while doing rotation animation. I don't think this will cause issues
on Andrid so I'm leaving it as is.

Bug: 891737
Test: covered by unittests.

Change-Id: Ic558ecccf594664d1f7b91b830aca33f5ba89d9f
Reviewed-on: https://chromium-review.googlesource.com/c/1257143
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596867}