GitLab

This is platform convention.

BUG=869564
TEST=as in bug

Change-Id: I3a4dbec12c5047219f255694eb4251405422e8fe
Reviewed-on: https://chromium-review.googlesource.com/1164307Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582363}

Changes:
Make the suggestion chip text length no longer than 192dip.

Bug: 872948
Change-Id: I54bc24cfc5b0ecf50d05e8312413e72ca14276e9
Reviewed-on: https://chromium-review.googlesource.com/1171676
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582362}

IWYU: std::unique_ptr needs <memory>. This fixes the libstdc++ build:

    In file included from ../../base/test/scoped_mock_clock_override.cc:5:0:
    ../../base/test/scoped_mock_clock_override.h:39:8: error: ‘unique_ptr’ in namespace ‘std’ does not name a template type
       std::unique_ptr<base::subtle::ScopedTimeClockOverrides> time_clock_overrides_;
            ^~~~~~~~~~

Bug: 818294
Change-Id: I3b92e51f2565b42869cf2400dd4d3654e112f0fb
Reviewed-on: https://chromium-review.googlesource.com/1170837Reviewed-by: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Raphael Kubo da Costa (CET) <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#582361}

This change allows the Captured Sites Automation Framework to replay
interactions on iframes. As part of this change, I switched the
automation framework to trigger the autofill popup by clicking on an
input field instead of pressing the 'DOWN' key, which does not work in
automation on some iframes.

Also included in this change is a fix I made to address the issue that
calling 'ASSERT' inside a test function does not abort the test.

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

In some situations the next Time Window Limit was not calculated correctly, this
caused the TimeLimitController to recalculate the time limit constantly.

Bug: 873228
Change-Id: I6b88792aa6849774778d85d8dea2695192acc172
Reviewed-on: https://chromium-review.googlesource.com/1171114Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com>
Cr-Commit-Position: refs/heads/master@{#582359}

This reverts commit 108f9e6cb07bdf3327b8b62e3ad43703b854662d.

Reason for revert: Just re landing now that gerrit is OK

Original change's description:
> Revert "Android: moving MediaUrlResolver tasks to thread pool"
> 
> This reverts commit d20f6cb34484fbd5e7ca2c651974d71c62e2f4d0.
> 
> Reason for revert:Due to Gerrit outage http://crbug.com/872722, we are reverting this CL. Please, re-land it after all clear is given. If you have questions, please ask on the bug. Sorry for the inconvenience.
> 
> Original change's description:
> > Android: moving MediaUrlResolver tasks to thread pool
> > 
> > Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
> > exector is good for preventing concurrency errors since it guarantees
> > serial execution, but bad for performance since the entire app shares
> > this single queue.
> > 
> > It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
> > since this use doesn't appear to rely on the concurrency guarantees that
> > SERIAL_EXECUTOR provides.
> > 
> > TBR= test file
> > Bug: 869907
> > Change-Id: I5770f3f0211d2c10b28f2290973bbfd57bee53f0
> > Reviewed-on: https://chromium-review.googlesource.com/1159236
> > Commit-Queue: Sam Maier <smaier@chromium.org>
> > Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
> 
> TBR=mlamouri@chromium.org,smaier@chromium.org
> 
> Change-Id: I5cd823a033bb6443007734d4faf0e1ddf98de648
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 869907
> Reviewed-on: https://chromium-review.googlesource.com/1169854
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>

TBR=mlamouri@chromium.org,tandrii@chromium.org,smaier@chromium.org

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

Bug: 869907
Change-Id: I31b02f5b543f2fdb8b0b089f241d79ceb720a626
Reviewed-on: https://chromium-review.googlesource.com/1171702
Commit-Queue: Sam Maier <smaier@chromium.org>
Reviewed-by: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582358}

TBR=crouleau@chromium.org

Change-Id: Id77c7546989bed6f3fdb269abdc2bc2e976ca4cd
Reviewed-on: https://chromium-review.googlesource.com/1171679Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582357}

Spec work has moved into the WICG repository, so update links:

Explainer: https://github.com/WICG/web-locks/
Spec: https://wicg.github.io/web-locks/

Bug: 161072
Change-Id: I450beb25d8a7c9c0a80b06b7e84d7ac8db3cece1
Reviewed-on: https://chromium-review.googlesource.com/1171213
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582356}

This reverts commit 3963b98d.

Reason for revert: Consistent failures in ProfileWindowWebUIBrowserTest.UserManagerFocusSingleProfile, see e.g. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20%2832%29%20Tests/36834

Original change's description:
> cros: In OOBE, turn off scrolling if the screen fits in the container
> 
> Bug: 855546
> Change-Id: I065c2bbd1e3db69dca3f8b18d40ce5beb09f9abd
> Reviewed-on: https://chromium-review.googlesource.com/1162715
> Reviewed-by: Jacob Dufault <jdufault@chromium.org>
> Reviewed-by: Alexander Alekseev <alemate@chromium.org>
> Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#582312}

TBR=alemate@chromium.org,jdufault@chromium.org,qnnguyen@chromium.org

Change-Id: Icd9a6648582e8c49bcdbd4bd79d844745d54c2a9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 855546
Reviewed-on: https://chromium-review.googlesource.com/1171703Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582355}

We used to store whether the target of pointerevent
has recieved pointerover event or not to handle this
correctly when capture gets active or lost. But since
then the spec has change which made this state
unnecessary.

Change-Id: I98eed286b47463d2e103495ec66750d01e3fe58b
Reviewed-on: https://chromium-review.googlesource.com/1169918Reviewed-by: Ella Ge <eirage@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582354}

This could be handled in Skia, but there's already a context option for
it, so just forward the workaround setting to that.

Bug: 829614
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
Change-Id: Iaeb625ea327b814d07854dd81eb0458598a0c137
Reviewed-on: https://chromium-review.googlesource.com/1169771
Commit-Queue: enne <enne@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582353}

This reverts commit c2af33f66d4079e4306fb698828d6d9d6d4fbe95.

Reason for revert: Just re landing now that gerrit is OK

Original change's description:
> Revert "Android: moving FileEnumWorkerTask to thread pool"
>
> This reverts commit 5eb802f9e1b7c765f77ec4a61f7f448731c36811.
>
> Reason for revert: Due to Gerrit outage http://crbug.com/872722, we are reverting this CL. Please, re-land it after all clear is given. If you have questions, please ask on the bug. Sorry for the inconvenience.
>
> Original change's description:
> > Android: moving FileEnumWorkerTask to thread pool
> >
> > Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
> > exector is good for preventing concurrency errors since it guarantees
> > serial execution, but bad for performance since the entire app shares
> > this single queue.
> >
> > It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
> > since this use doesn't appear to rely on the concurrency guarantees that
> > SERIAL_EXECUTOR provides.
> >
> > Bug: 869907
> > Change-Id: I266476c44f16ade391dfef0e5a99d33494312598
> > Reviewed-on: https://chromium-review.googlesource.com/1161089
> > Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
> > Commit-Queue: Sam Maier <smaier@chromium.org>
>
> TBR=finnur@chromium.org,smaier@chromium.org
>
> Change-Id: I890bfff82b7471f54948c03dea7d2820224e978f
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 869907
> Reviewed-on: https://chromium-review.googlesource.com/1169851
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>

TBR=finnur@chromium.org,tandrii@chromium.org,smaier@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.
TBR=Gerrit reland

Bug: 869907
Change-Id: I4e07a7d43ae7f0af01a248f4c41d42699d041f30
Reviewed-on: https://chromium-review.googlesource.com/1171427Reviewed-by: Sam Maier <smaier@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582352}

Change-Id: I327542d2ec81be8d3d4240a82f7121c27c4994b3
Reviewed-on: https://chromium-review.googlesource.com/1169427Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582351}

for both the active tab and the toolbar. This matches the bookmarks
bar, i.e. PaintBackgroundAttachedMode.

Bug: 866974
Change-Id: I3a86d2330bf09903f74359e433a4165e3e4d3e8e
Reviewed-on: https://chromium-review.googlesource.com/1171216
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582350}

In particular, move Net.CertificateTransparency.MainFrameValidSCTCount
from ResourceDispatcherHost to NavigationURLLoaderImpl.

Bug: 859364
Change-Id: I2258fc36af30b64b76eb7c5bc2c1f9851bb0f1be
Reviewed-on: https://chromium-review.googlesource.com/1168093
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582349}

This is to reflect non-forwards / non-backwards compatible changes to
the interface between rtanalytics_main and librtanalytics.so due to the
changes to incorporate the use of the Mojo IPC-based video capture
service.

Bug: 871884
Change-Id: I97c92be7143609026d34e824b29f524e1f386f11
Reviewed-on: https://chromium-review.googlesource.com/1165824Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Luke Sorenson <lasoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582348}

Creating an abstraction called CastAudioFocusRequest to handle backwards
compatibility of AudioFocus methods in AudioManager.

Merge-With: eureka-internal/191659
Bug: 112064938
Test: junit test
Change-Id: I914cec6a6bd2179f02ab5fd6959fcf3157b3e637
Reviewed-on: https://chromium-review.googlesource.com/1165884Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Commit-Queue: Shyamsundar Parthasarathy <shyamsundarp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582347}

This CL allows for WebMediaPlayerMS to create a SurfaceLayerBridge and
interface with it in order to use a Surface for video playback.

Bug: 746182
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I39174499a7e659eeeef13a81f8f5679d5f73425a
Reviewed-on: https://chromium-review.googlesource.com/1087587Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582346}

The WebViewBrowserPluginSpecificTest class includes tests which use a
BrowserPluign-based GuestView. Since all GuestViews except MimeHandlerViewGuest
are now based on cross-process frames, these tests should not be implemented as
WebViewGuest tests anymore.

This CL introduces a new chrome browser test target for such
BrowserPluginSpecific tests where the tests instantiate a MimeHandlerViewGuest
instead of a <webview>.

Ideally, the tests should have lived with the rest of MimeHandlerViewTests in
extension layer; however, due to chrome layer dependencies it is not possible.

Bug: 659750, 533069, 330264, 870604
Change-Id: Ica252a60e94bad47cabbff8b9275b8f9fb05d7ae
Reviewed-on: https://chromium-review.googlesource.com/1168734
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582345}

The symbolization in the Fuchsia runner scripts is not set up to work
with debug information partly split from the binary.

Bug: 777008
Change-Id: Iedaf4fe56cc8092af21acfd0d244304982a6035c
Reviewed-on: https://chromium-review.googlesource.com/1170440Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582344}

R=proberge

Bug: 872748
Change-Id: I42ae9acf6bd189ef45543ddfa15521262c56b95f
Reviewed-on: https://chromium-review.googlesource.com/1171549Reviewed-by: proberge <proberge@chromium.org>
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582343}

Removed ExternalURLTabUsageRecorderTestCase since it contains only one
disabled Earl Grey test. After some evaluation of the intention of the
test, it is not clear what purpose it serves/served or whether the code
being tested isn't already covered by unit tests.

Bug: 852341
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I988f4fc5512b40f331db565af2424e03b5c23b79
Reviewed-on: https://chromium-review.googlesource.com/1171365Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582342}

Adding an entry 'guest_view' for all GuestView related files.

Subscribing myself, wjmaclean@, and mcnee@ to the list.

Bug: None
Change-Id: I7751b3cb6d8b3163cdc7f1a11342a56a9cd2849b
Reviewed-on: https://chromium-review.googlesource.com/1171215Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582341}

These three roles are part of reaching role parity with HTML5. As such,
they should be exposed via platform accessibility APIs in the same way
as their native host language counterparts. Thus just add them to the
map of ARIA roles to internal roles.

Bug: 849650
Change-Id: I9a513e187a5beccd57fc5c7306929b0fd194b6dd
Reviewed-on: https://chromium-review.googlesource.com/1169476
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582340}

This avoids recomputing them later.

Also, changes RunOldLayout to use legacy layout to
compute border/padding to store on the fragment,
which seems more correct.

R=eae@chromium.org

Bug: 635619
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Id659d7c92eae81431d8e75a26ac3973421afc3d0
Reviewed-on: https://chromium-review.googlesource.com/1169634
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582339}

This reverts commit 306be5bf.

Reason for revert: GS bucket names have been fixed

Original change's description:
> [ChromeDriver] Fix path for old Chromium snapshots
> 
> Chromium snapshots before revision 579575 are still archived using
> the old directory name.
> 
> TBR=crouleau@chromium.org
> 
> Change-Id: I4cc1e9ca51af9f8f21e22214af2110a6d8be8fe7
> Reviewed-on: https://chromium-review.googlesource.com/1158709
> Reviewed-by: John Chen <johnchen@chromium.org>
> Commit-Queue: John Chen <johnchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#579802}

TBR=crouleau@chromium.org,johnchen@chromium.org

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

Change-Id: I093548f1d0ef02a37ffd8d3d2fe66f7222234e1b
Reviewed-on: https://chromium-review.googlesource.com/1171426Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582338}

Instead, dirty them on particular PaintLayers only when their layout changed.

Bug: 410867
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Idf7664b869b1e7205e68adc075bcf828f279cffb
Reviewed-on: https://chromium-review.googlesource.com/1168142Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582337}

display::Screen (and ScreenMus) now has the display for new windows,
so we can use that when making new browser windows under both mash
and classic ash. Likewise, we can use display::Screen (as ScreenAsh)
for new windows inside of ash.

This lets me remove ShellStateClient, a different mechanism that
accomplishes the same goal in a less general way.

Leave ash::ShellState for now. I will clean that up in a separate CL.

TBR=tsepez@chromium.org

Bug: 764009
Test: existing browser_tests for browser frame/size
Change-Id: I5c255dc2bf8fdd48f519f148d29aca3d37e7ae73
Reviewed-on: https://chromium-review.googlesource.com/1168197Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582336}

Bug: b/112447220
Test: Manual Test
Change-Id: Idcab08aca234f9f5528529aedb71fbbbdfa29d1d
Reviewed-on: https://chromium-review.googlesource.com/1171551Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582335}

As part of onion souping domstorage this adds a couple of new classes
to blink more or less duplicating the content equivalents:

CachedStorageArea matches content::LocalStorageCachedArea (with some
minor API changes, in particular around how it acquires a mojom
StorageArea). Also has improved test coverage compared to the content
version.

MockStorageArea is very similar to content::MockLevelDBWrapper (with
the difference that it doesn't implement StoragePartitionService since
it doesn't need to with the changed API of CachedStorageArea).

Bug: 781870
Change-Id: Ic64b3bf307fe275d9287669743f186c8470847bb
Reviewed-on: https://chromium-review.googlesource.com/1166218Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582334}

One of them lives on in browser because the Ash version trips a dcheck
when run in classic Ash mode.

Bug: 854704
Change-Id: I7822cc088c255b8c16c91cb1b5304c5e2b974115
Reviewed-on: https://chromium-review.googlesource.com/1170127
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582333}

Remove chasej from background_sync and tweak inclusions for
origin_trials.

Change-Id: Ie3f19642c491d791f5681ca92e15b34002b51d2e
Reviewed-on: https://chromium-review.googlesource.com/1171563Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Jason Chase <chasej@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582332}

Add a function to ServiceWorkerContextWrapper which starts a service worker and keeps it alive indefinitely.

This is only for use in ChromeOS for the Android Web Messages native integration.

Change-Id: Id2357f54078c12db0ad25cd9fe0622d57e34a064
Bug: 850823
Reviewed-on: https://chromium-review.googlesource.com/1119580Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Jon Mann <jonmann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582331}

Support for file-based persistence was removed in r571588,
so its no longer necessary for Cronet to explicitly create
a CertVerifier to guarantee it is a CachingCertVerifier.

Bug: 590875
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I23e9e6db12225a7474ce589d9333595729108f1c
Reviewed-on: https://chromium-review.googlesource.com/1169822Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582330}

These histograms are used, both within Chrome and within Google, in the
effort to identify and fight unwanted software and malware.

As such, I'm giving them a longer expiration date: two years.

Bug: 871482
Change-Id: I320976f7a18dfa3c5c0d6bb6c3bf05ddfec8e5b4
Reviewed-on: https://chromium-review.googlesource.com/1166197Reviewed-by: Chris Sharp <csharp@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582329}

Bug: 797292, 859594

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Id4e90f0ebdf5ac172b12c92d80b54348125bc883
Reviewed-on: https://chromium-review.googlesource.com/1171556Reviewed-by: Chris Mumford <cmumford@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582328}

Before: https://screenshot.googleplex.com/5YhNTQYuHV1
After: https://screenshot.googleplex.com/thg0VSMKzNX


Bug: 855186
Change-Id: I64b1ca9452330a847512c45220bda9173e1a1ac1
Reviewed-on: https://chromium-review.googlesource.com/1170141
Commit-Queue: Manas Verma <manasverma@google.com>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582327}

Historically, we haven't been running these WebGL perf tests
on our Android perf bots (which are all Qualcomm devices).
This change should hopefully allow us to start tracking WebGL
perf on mobile.

Bug: 867368
Change-Id: I8e409d649f6238094928dfdac4cc6f7d2c444ca5
Reviewed-on: https://chromium-review.googlesource.com/1170032Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582326}

Inline reply on lock screen is not launched at the same time as
the lock screen notifications. So this CL creates a separate feature
flag for inline reply.

Bug: b/111391270

Change-Id: I585beba17b3a491ce495f1d6c35ce46b2a6b6686
Reviewed-on: https://chromium-review.googlesource.com/1166617
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582325}

This CL adds a new MessagePumpForUI::Observer class, which can be used to get
notifications pre and post MSG dispatch.

Change-Id: I16b0df6d30b41f04f124d4b64d850c278f2c10d9
Reviewed-on: https://chromium-review.googlesource.com/1166164
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582324}