GitLab

Since Bluetooth power preference became user-specific, we disallowed
non-primary users to change Bluetooth power setting for UX consistency
with system tray.

Bug: 853374
Change-Id: If61d2c0c048e7d8c764e24798da0ebbf2ab6c68f
Reviewed-on: https://chromium-review.googlesource.com/1187601
Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586088}

This CL adds ref count to a ServiceWorker while dispatching an
extension event to it. The ref count is decreased when we receive an
ack for worker thread, similar to vanilla extension events.

This CL adds the event ack IPC from worker thread to browser process.

The ref counting methods in //content (Starting/FinishedExternalRequest)
requires service worker version id within a SWContext, this CL adds
support for this:
  - in browser process: EventListeners now also include service
    worker version id.
  - in browser process: ServiceWorkerContext::StartWorkerForPattern
    returns version id along with existing information (render process
    id and worker thread id). ServiceWorkerTaskQueue uses it to
    dispatch event through EventRouter.
  - in worker thread: ScriptContext of a worker also stores the
    version id, used while sending event ack from WorkerThreadDispatcher.

Bug: 876207
Change-Id: Ia0d2df39091ac07504444523020fef9579e42696
Reviewed-on: https://chromium-review.googlesource.com/1175420
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586087}

When we seek a video being casted with the FlingingRenderer, time never
gets updated on the phone after the seek completes. This is because
Blink doesn't get the appropriate seek completion signals, since WMPI's
buffering state never goes back to BUFFERING_HAVE_ENOUGH.

This CL fixes issue by always returning BUFFERING_HAVE_ENOUGH in
FlingingRenderer::StartPlayingFrom(). Because there is no need to buffer
when using the FR, we can always consider the media pipeline to be fully
buffered. Sending a buffering state change in StartPlayingFrom() might
be suprising, but we do the same with the MediaPlayerRenderer, and it
has not caused any (known) problems so far.

Bug: 875517
Change-Id: If6069d501af12ec20f844d0adc1ea980935fb99f
Reviewed-on: https://chromium-review.googlesource.com/1184060
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586086}

This should guard against a crash.
It's not clear exactly what the cause of this null is, but it's
probably some kind of failure to allocate the SkImage (e.g.
out-of-memory, GPU process loss, or other unpredictable failure case).

Bug: 852303
Change-Id: I10a817f2dccd801f5834be343ad687af09e06721
Reviewed-on: https://chromium-review.googlesource.com/1188515Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586085}

This simplifies many conditions around the code in
chromeos/components/tether.

Bug: 561800
Change-Id: I69c25666ae1b1362df6df67889a9a45226961387
Reviewed-on: https://chromium-review.googlesource.com/1188060Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: DongJun Kim <djmix.kim@samsung.com>
Cr-Commit-Position: refs/heads/master@{#586084}

Avoids linker errors from LLD about -Wl, not being a recognized command
line flag.  This will fix the Windows CFI and ThinLTO FYI bots.

Factor out a variable for the optimization level so we need one less
conditional.

TBR=agreive@chromium.org, agrieve@chromium.org, gbiv@chromium.org, pcc@chromium.org

Bug: 807147
Change-Id: I8a928eaab93ec181ba057cdda4cb635389f30926
Reviewed-on: https://chromium-review.googlesource.com/1188879Reviewed-by: Reid Kleckner <rnk@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586083}

Replace the GPU.DirectComposition.SwapBuffersFailed UMA which was being
emitted on failure only with SwapBuffersResult which is emitted on both
success and failure.

Bug: 869677
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: If950beb70d22f64997e7533751abcf9448d608db
Reviewed-on: https://chromium-review.googlesource.com/1187128
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586082}

This reverts commit bfb341f2.

Reason for revert: No longer necessary to attempt to expand
SSHPortForwarder's functionality to support bidirectional port mapping.
Original change's description:
> [Fuchsia] TestServer rework for new SSHPortForwarder functionality.
>
> Made a minor change to make sure that SetupTestServer interacts
> properly with the new _ConnectPortForwardingTask and ForwardingScheme
> versions.
>
> Change-Id: I16add737f7595fac416973c1296882f9f40d0dc1
> Reviewed-on: https://chromium-review.googlesource.com/1178381
> Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
> Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#583900}

TBR=kmarshall@chromium.org,sergeyu@chromium.org,stephanstross@google.com

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

Change-Id: I1fd3a0f48cc21fba0d599a9fba26a62aa04e5dc1
Reviewed-on: https://chromium-review.googlesource.com/1188493
Commit-Queue: Stephan Stross <stephanstross@google.com>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586081}

autofill_jni_headers used to run for
components/autofill/browser/android/java/src/org/chromium/components/browser/autofill/PersonalAutofillPopulator.java
in the old gyp build, but that file has been removed in crbug.com/403872.

Bug: 403872
Change-Id: I7551a517087e1da2d3ebede156107ca358712aa7
Reviewed-on: https://chromium-review.googlesource.com/1187764Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586080}

This policy allows administrators to prohibit users from utilizing the
upcoming feature which allows users to sync their SMS messages between
their laptops and phones.

Bug: 870113, 824568
Change-Id: I12515b75c1f62d5c99bfb1a0adacddad80de0196
Reviewed-on: https://chromium-review.googlesource.com/1187730Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586079}

In GTK4, the GDestroyNotify that SelectFileDialogImplGtk used does not get fired
when the GtkFileChooser is closed (perhaps GTK is now doing some lazy
deletion?).  But the "destroy" signal does get fired, so move the event
re-enabling code there.

Also clean up some messy code.

BUG=876586
R=sky

Change-Id: I2d78ff292d167fe526bd5fb35aaf6296d32da1af
Reviewed-on: https://chromium-review.googlesource.com/1188585Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586078}

This behaves similar to DelegatedFrameHost. As discussed in
https://chromium-review.googlesource.com/c/chromium/src/+/1173663,
this implements composition instead of inheritance.

Bug: 859977
Change-Id: Icf5e0c83c4b3789a2173933a26067c6275f62765
Reviewed-on: https://chromium-review.googlesource.com/1186199Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Xing Xu <xing.xu@intel.com>
Cr-Commit-Position: refs/heads/master@{#586077}

This CL updates the What's New texts to reflect these changes:
* Between Android client M61 and M70
* Between iOS client M67 and M70

Bug: 877704
Change-Id: Ifb3aff593c1bfc3a8b1f02f018dd458670c3100e
Reviewed-on: https://chromium-review.googlesource.com/1189055Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586076}

This CL includes concrete implementations for the abstract Executor
classes defined in the Nearby library. A ScheduledExecutor allows
scheduled tasks that asynchronously execute in the future. A
MultiThreadExecutor allows tasks with or without return values to be
asynchronously executed in parallel, and a SingleThreadExecutor allows
tasks with or without return values to be executed asynchronously, but
in sequence relative to each other.

Because the actual Nearby library has yet to be merged into the CrOS
directory, this CL includes stand-in Nearby abstract classes under
the temporary directory //chromeos/components/nearby/library.
This directory will be removed after the Nearby library gets imported
to //third_party.

Bug: 861813
Change-Id: Idc561f2cedea7360eaf6d74940e1be8e56efe7cb
Reviewed-on: https://chromium-review.googlesource.com/1154134
Commit-Queue: Kyle Qian <kyleqian@google.com>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586075}

This reverts commit acf1c986, which
speculatively reverted the change to establish whether it might be
responsible for a spike in BlobReader crashes. Re-landing now, since the
revert had no impact on crash rate of that signature in Canary (see
https://crbug.com/864351).

- Use a base::AutoReset instance to manage a single integer tracking
  whether the completion callback for an operation is invoked before
  we have actually returned to the caller.
- Remove the now-unused OperationHandle and BeginOperationScoper.
- Replace SupportsWeakPtr with an internal WeakPtrFactory.
- Replace potentially unsafe use of GetWeakPtr() with a |weak_ptr_|
  member.
- Temporarily disables the recently-added FileSystemURLLoaderFactoryTest
  tests, which have incorrect threading, causing WeakPtr checks to
  fire.

TBR=wez@chromium.org,rockot@chromium.org,alemate@chromium.org,noel@chromium.org,mek@chromium.org,fukino@chromium.org,cmumford@chromium.org,govind@chromium.org,tzik@chromium.org,abdulsyed@chromium.org

Bug: 846985, 860547, 864351
Change-Id: Ia843811a2e85be9347f410ec9f97dc3dc0f1713a
Reviewed-on: https://chromium-review.googlesource.com/1189048
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586074}

Bug: 731383
Change-Id: Id563bd36de50c7685a524336906fc8542d1c6f51
Reviewed-on: https://chromium-review.googlesource.com/1188451Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Commit-Queue: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586073}

Specifically the mojoms in services/ws now are all in the ws namespace.

BUG=876924
TEST=covered by tests
TBR=msw@chromium.org,tsepez@chromium.org

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ib92b167f8b528b6c0423ec4be99e25558d1d43da
Reviewed-on: https://chromium-review.googlesource.com/1189030Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586072}

App ranking system uses install time in case launch time is not
available to rank apps. We don't want apps, installed by policy or by
default appear in recent app. This CL extends app ranking system by
handling such apps. Previously we had ARC apps folled by this approach
by not-setting install time installed internally apps. However this was
not good once install time should not depend on ranking system. So this
CL makes ranking centralized and switch ARC and Extension apps to it.

TEST=Manually + unit tests added.
BUG=757639

Change-Id: If567e7e72908c0186e3096b1e83fa917df47d082
Reviewed-on: https://chromium-review.googlesource.com/1188591
Commit-Queue: Yury Khmel <khmel@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586071}

This CL includes a concrete implementation for the abstract classes
Lock (which must be recursive) and ConditionVariable defined in the
Nearby library.

A related CL was previously abandoned
(https://chromium-review.googlesource.com/c/chromium/src/+/1138871)
because the Nearby C++ library already includes a DefaultLock and
DefaultConditionVariable. However, that CL is being revived as this CL
because a Chromium-specific Lock/CV implementation is required. For
instance, Chromium requires a ScopedBlockingCall to be instantiated in
scopes where blocking calls are made. DefaultConditionVariable does not
include an instantiation of ScopedBlockingCall. This implementation of
ConditionVariable uses a base::WaitableEvent, which instantiates a
ScopedBlockingCall. This CL also includes a Lock implementation that is
recursive, which is a requirement of Nearby, but is not originally
supported by base::Lock.

Because the actual Nearby library has yet to be merged into the CrOS
directory, this CL includes stand-in Nearby abstract classes under
the temporary directory //chromeos/components/nearby/library.
This directory will be removed after the Nearby library gets imported
to //third_party.

Bug: 861813
Change-Id: I72660ed302e239d8f38a21728fc715b000057c13
Reviewed-on: https://chromium-review.googlesource.com/1145730
Commit-Queue: Kyle Qian <kyleqian@google.com>
Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586070}

remove the manual source list and use the auto-generated one.

BUG=872521
TEST=bots
R=nednguyen@chromium.org,kbr@chromium.org,nednguyen@google.com

Change-Id: Ic5d00299edc39af23802db71c43ad0716669837d
Reviewed-on: https://chromium-review.googlesource.com/1188901Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586069}

Create a utility method to unify the way we create image buttons. This
turns on default ink drop click and focus styles and make them focusable.

Test: manually build and test
Bug: b:112925587
Change-Id: I70c72e033fae2dbad39034d716483c77ea578161
Reviewed-on: https://chromium-review.googlesource.com/1186137
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Muyuan Li <muyuanli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586068}

It seems that Event's root_location is in display's coordinate
in WindowTreeClient (i.e. browser). This could complicate the
coordinate conversions like aura::ScreenCoordinateClient and
cause problems like crbug.com/876509.

Since root_location is relative to the root window in desktop
aura (like desktop Linux), I believe we want to do so too on
Mash.

This is actually contradicting with crrev.com/583488 but
I believe this is better for us.

Bug: 876509
Test: unit tests pass, manually checked crbug.com/873763 behavior
Change-Id: I51f03772e2872783cf5fb9ce78cdcfe3dd7b0e67
Reviewed-on: https://chromium-review.googlesource.com/1187134
Commit-Queue: Jun Mukai <mukai@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586067}

These tests were disabled by https://crrev.com/c/1176206 because
they were reported as flaky on debug builds. Based on the
flakiness dashboard, it appears the failures were timeouts on the
Win10 Tests x64 (dbg) bot. interactive_ui_tests is marked as
experimental on this bot due to crbug.com/840369. The
webui_polymer2_interactive_ui_tests suite is expected to have the same
behavior, so it should also be marked as experimental on this bot.

Remove the tests from the blacklist, as they should pass on other bots.

Bug: 875443
Change-Id: Ib5b3c99cf589b1ab9994346460e95ed746533ba6
Reviewed-on: https://chromium-review.googlesource.com/1187729Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586066}

This is a reland of a2a4e75d with a
work-around for cronet_tests' sharing libbase.so with libcronet.so in
component builds.

- Move some APIs off of base::TestSuite, that we unnecessarily public.
- Rename the various internal TestEventListeners to express purpose.
- Add CheckForLeakedGlobals check, and DisableCheckForLeakedGlobals API.
  The latter is called by the content::ContentTestSuiteBase, since the
  various browser- and ui-tests running under that suite base run more
  like the browser itself, and so are expected to let global singletons
  leak.

If tests fail or flake due to this patch, then this indicates that the
test is actually leaking global state that may break other tests if they
happen to run in the same process, leading to hard-to-diagnose flakes.

There are two main failure cases:
If the test directly or indirectly uses TaskScheduler, but does not
create a ScopedTaskEnvironment, then please add one to the test, or to
the test base-class, as appropriate, to fix it.
If the test suite cannot be fixed in this way then please add a call to
DisableCheckForLeakedGlobals(), with a comment linking to a bug for the
issue.

TBR: gab, sky, mef
Bug: 875486, 877355, 744567
Change-Id: Iaea38d24ede271c248a3abb0b3f7ee931c2538f5
Reviewed-on: https://chromium-review.googlesource.com/1187783Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586065}

This field was dropped by a revert, but we have data for it, so re-add the description.
https://crrev.com/d38f4e3c1225c36574911f6fdeecdb1b236dd054

Change-Id: Ie68bc76ced75a1d6269b252801cda76baa5de9ff
Reviewed-on: https://chromium-review.googlesource.com/1188765Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586064}

Fixes network_service_content_browsertests RenderThreadImplBrowserTest.NonResourceDispatchIPCTasksDontGoThroughScheduler
failing to find the utility service process exe on Windows, like:
[FATAL:utility_process_host.cc(263)] Check failed: false. Unable to get utility process binary name.

Bug: 876947
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ia7f51366e4b4db27ec8c3bbee3d57866c1bd67b9
Reviewed-on: https://chromium-review.googlesource.com/1185628
Commit-Queue: Matt Mueller <mattm@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586063}

FrameViewAutoSizeInfo should not add hypothetical vertical scrollbar
space when we already have a real vertical scrollbar.

The real scrollbar is included in the LayoutView's preferred width
(since crrev.com/397112).  If the redundant accomodation makes the
scrollbar detectably unnecessary, the next autosize reduces the width,
making it appear again.

The autosized FrameView now accomodates exactly one vertical scrollbar
in this scenario, instead of infinitely bouncing between two and zero.
The scrollbar could actually be removed even at this size, but the code
isn't smart enough to detect that.

Bug: 838150
Change-Id: I23dce5a37faed33de978e1d2182009a2fe0c6fd1
Reviewed-on: https://chromium-review.googlesource.com/1188767Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586062}

This change decouples the mouse/keyboard input monitors from
ClientSessionControl and allows them to be used for other purposes.

Bug: 877176
Change-Id: Idcefa8a8dd1d36bb57f83b8a27d8aba90981466f
Reviewed-on: https://chromium-review.googlesource.com/1189027Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586061}

The flaky tests are:

external/wpt/editing/run/delete.html?1-1000
external/wpt/editing/run/delete.html?1001-2000
external/wpt/editing/run/delete.html?3001-4000
external/wpt/editing/run/delete.html?4001-5000
external/wpt/editing/run/delete.html?5001-6000
external/wpt/editing/run/delete.html?6001-last
external/wpt/editing/run/forward_delete.html?1-1000
external/wpt/editing/run/forward_delete.html?1001-2000
external/wpt/editing/run/forward_delete.html?2001-3000
external/wpt/editing/run/forward_delete.html?3001-4000
external/wpt/editing/run/forward_delete.html?4001-5000
external/wpt/editing/run/forward_delete.html?5001-6000
external/wpt/editing/run/forward_delete.html?6001-last

external/wpt/editing/run/delete.html?2001-3000 isn't in this list since
it's already disabled elsewhere in this TestExpectations file.

TBR=foolip@chromium.org

Bug: 877104
Change-Id: I01dd8218bddc9c1c726da03a062a714fc4f1f56c
Reviewed-on: https://chromium-review.googlesource.com/1188896Reviewed-by: Scott Little <sclittle@chromium.org>
Commit-Queue: Scott Little <sclittle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586060}

Scenic is the only ozone platform usable on fuchsia. Previously,
when compiling with is_chromecast=true the cast platform was enabled,
so cast_shell wasn't compiling properly.

Bug: 877264
Change-Id: If40c4ad28678015a2e357f86336cf56e1c484ac7
Reviewed-on: https://chromium-review.googlesource.com/1187654Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586059}

This patch copied 'clear_site_data_throttle.h/.cc' into
'clear_site_data_handler.h/.cc' with the following differences:
1. The new handler will be called through the |NetworkServiceClient|
   pipeline to work with Network Service.
2. The new handler doesn't have special handling for Service Worker.
  * The assumption is that the response from network process
    (NetworkServiceClient) won't be modified by Service Worker.
3. The new handler won't defer console messages for navigations. Future
   works could fix this to match current behavior (marked as TODO).
4. The new handler will always defer the request if it has
   'Clear-Site-Data' header, and resume after the browser finished
   processing.

We have to duplicate the codepath because
|NetworkServiceNetworkDelegate| currently doesn't work without Network
Service, and the new handler interface has no information about Service
Worker.

This patch fixed all Clear-Site-Data related tests (10 browser tests
and 2 layout tests).

crbug.com/876931 tracks remaining non-Canary blocking TODOs.

Bug: 721398
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I065140ab49ab3647cba0e64717440d0f1bf42095
Reviewed-on: https://chromium-review.googlesource.com/1170200
Commit-Queue: Chong Zhang <chongz@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586058}

https://skia.googlesource.com/skia.git/+log/1118cfdbdcc2..92bc476c8c49


git log 1118cfdbdcc2..92bc476c8c49 --date=short --no-merges --format='%ad %ae %s'
2018-08-24 herb@google.com Rearrange templates to get ios to compile
2018-08-24 scroggo@google.com Revert "Reland "Switch SkCodec to use skcms" plus fixes"
2018-08-24 robertphillips@google.com Fix drawRect
2018-08-24 herb@google.com Have GPU and RemoteGlyphCache share mask position code
2018-08-24 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 8ca60805916f..337bd6984078 (2 commits)
2018-08-24 liyuqian@google.com Remove gclient sync from calmbench
2018-08-24 herb@google.com Add back tight scaler context managment
2018-08-24 allanmac@google.com Cut-and-paste typo was limiting concurrency
2018-08-24 scroggo@google.com Reland "Switch SkCodec to use skcms" plus fixes
2018-08-24 brianosman@google.com Reland "match sRGB primaries with skcms"
2018-08-24 ethannicholas@google.com fixed skslc's nested conditional break detection
2018-08-24 herb@google.com Reorganize TrackLayerDevice and move processGlyphRunForMask
2018-08-24 robertphillips@google.com Suppress failing Vulkan test on IntelHD405
2018-08-24 kjlubick@google.com [PathKit] Write more complete docs and clean up API to be consistent


Created with:
  gclient setdep -r src/third_party/skia@92bc476c8c49

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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=master.tryserver.blink:linux_trusty_blink_rel;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=fmalita@chromium.org

Change-Id: Ib5356de96cb02bd534c76b2a390ef6212fdb6144
Reviewed-on: https://chromium-review.googlesource.com/1188924Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#586057}

This clarifies dependency on test filter data, since
it is only used by the "test" template.

Also, it paves the path for building v8 on Fuchsia
standalone: the "fuchsia_package_runner" template
can be used directly in v8 repo, and in v8-only
checkout.

Change-Id: Ibe171c48ee818cc5b722294f682f83c3ae240908
Reviewed-on: https://chromium-review.googlesource.com/1180731Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Dimitri Glazkov <dglazkov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586056}

CSP can prevent eval and will cause this error:
"refused to evaluate a string as javascript because 'unsafe-eval'"

This fails silently on iOS so we need to catch it.

Bug: 686364
Change-Id: I5de275576670846dffc29f9f2c3916259196e70f
Reviewed-on: https://chromium-review.googlesource.com/1183944Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: John Wu <jzw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586055}

Bug: 875088
Change-Id: Ic5edb56d0621c6685d6cb1cfe03f54e57990c068
Reviewed-on: https://chromium-review.googlesource.com/1182670
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586054}

Bug: 848821
Change-Id: I5e0dd225cdf7163e159286352a096c9cffe1d32b
Reviewed-on: https://chromium-review.googlesource.com/1188965Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586053}

Previously Chromecast used to upload crash reports from debug/eng
builds to crash-staging/ server. But according to crash-users@ the
staging server was only meant for internal testing, we shouldn't be
using it. Instead we should upload all our crashes to the main crash/
server. Chrome and ChromeOS already upload all their crashes, from all
channels including dev and canary, to the main server. And this CL will
make Chromecast to always use the main server as well.

Bug: 112111490
Change-Id: Ic94ba1ba7d52d7188bb2fcfb6149cb734715b7d4
Reviewed-on: https://chromium-review.googlesource.com/1161004
Commit-Queue: Sergey Volk <servolk@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586052}

There is no extra 'cmake' path component after bin on Linux.
Hopefully this will resurrect the Linux Clang ToT bots after
https://crrev.com/585976.

TBR=hans@chromium.org
NOTRY=True

Bug: 797991
Change-Id: I7e1e38e824c8986303a9ec1972bb5f57a2cd9bea
Reviewed-on: https://chromium-review.googlesource.com/1189034Reviewed-by: Reid Kleckner <rnk@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586051}

Bug: 835029
Change-Id: I6b483f66203120d3684c0da6ba29bf9997116cee
Reviewed-on: https://chromium-review.googlesource.com/1164251
Commit-Queue: Yue Cen <rsgingerrs@chromium.org>
Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586050}

https://pdfium.googlesource.com/pdfium.git/+log/ce26d7d03d6c..e6ff2ebfaa19


git log ce26d7d03d6c..e6ff2ebfaa19 --date=short --no-merges --format='%ad %ae %s'
2018-08-24 tsepez@chromium.org Rename CFX_DIBSource to CFX_DIBBase.
2018-08-24 tsepez@chromium.org Use span<uint8_t> in more fxcodec code.
2018-08-24 npm@chromium.org Cleanup CalculateBaseSpace in CPDF_TextPage


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

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: Id69be6a3555fb225e9caff406ea93da4c669b176
Reviewed-on: https://chromium-review.googlesource.com/1188925Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#586049}