GitLab

Bug: 808113
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I2b475e6fd474c900ed1984010d15a3e1e31c2af0
Reviewed-on: https://chromium-review.googlesource.com/922930
Commit-Queue: Daniel Blakemore <danblakemore@google.com>
Reviewed-by: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537373}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=kbr@chromium.org

Change-Id: I90d8149cf7352e70793b2d4b7e94ffe33f3f7b72
Reviewed-on: https://chromium-review.googlesource.com/924162Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537372}

This implements the hooks from the LayoutCustom object into a web
developer defined layout class.

See: https://drafts.css-houdini.org/css-layout-api/#invoke-a-layout-callback

Currently the only useful thing this does to allow the web developer to
return an "auto" block-size, e.g.

registerLayout('foo', class {
  *intrinsicSizes() {}
  *layout() {
    return { autoBlockSize: Math.random() * 100; } // FUN!
  }
});

The engine calculates the inline-size, and adjusts the block-size for the
web developer. This is a simplification on the current API as spec'd but
we'll see what the HoudiniTF thinks of this approach.

The other large behaviour change is appropriate "fallback" handling when
something goes wrong. See "fallback" tests.

Bug: 726125
Change-Id: I08cd2e439f4321bd534a4e3f7222fbdb898e1785
Reviewed-on: https://chromium-review.googlesource.com/917423Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537371}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=haraken@chromium.org

Change-Id: I294dede7daefd705b508bb78c4bf0c2dedc8a2a9
Reviewed-on: https://chromium-review.googlesource.com/924170Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537370}

This removes the ExperienceSamplingPrivate extension API, which was used
only by the CUES extension (which is no longer in use). This also
removes all the instrumentation code that triggered the extension events
throughout the code base, and deprecates entries in enums.

Bug: 810420
Change-Id: Ia155ad3feada4bac147f0960e05065c44d6978a3
Reviewed-on: https://chromium-review.googlesource.com/915121
Commit-Queue: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537369}

Bug: 812710
Change-Id: I4344c258668c5017a0a145e487ca2eb526bd49bc
Reviewed-on: https://chromium-review.googlesource.com/923281Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#537368}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=bauerb@chromium.org

Change-Id: I5743df2f237a1dd0f88e880b96abf6a0aea3b1d3
Reviewed-on: https://chromium-review.googlesource.com/924165Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537367}

https://skia.googlesource.com/skia.git/+log/f6f7b67ac230..50d4a6a66190

$ git log f6f7b67ac..50d4a6a66 --date=short --no-merges --format='%ad %ae %s'
2018-02-16 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ c42baa572..0fb1530a0 (1 commit)
2018-02-16 bsalomon Fix nullptr access when ProcessorOptimizationValidationTest fails
2018-02-16 herb Add a generalized array of bytes with a given alignment
2018-02-16 jvanverth Add an actual config for GPU NativeFonts tests
2018-02-15 mtklein register SIGTERM handler in DM
2018-02-15 caryclark improve bookmaker defines and references
2018-02-15 brianosman Fix flicker when changing backend on iOS viewer
2018-02-15 fmalita Generic "directory" viewer slide
2018-02-15 brianosman Avoid creating MIPs until necessary when MIP bias is active

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=caryclark@chromium.org

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

Bug: 780960
Change-Id: I14e6af96907933791e11690e4268af2fa00624c8
Reviewed-on: https://chromium-review.googlesource.com/920721
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537365}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

Change-Id: I30f5818ba05186b917e88c64fe7f21ff7255a12a
Reviewed-on: https://chromium-review.googlesource.com/924088Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537364}

This removes the necessity of including content_verifier_delegate.h
where only ContentVerifierKey would be required.

Bug: 796395
Change-Id: Icf18f2957291c454c6e8a6971f98be7f9fd2fb78
Reviewed-on: https://chromium-review.googlesource.com/922925
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537363}

This CL adds logic to cancel all scrubbing state in MediaControlsImpl
and MediaControlTimelineElement when the controls are hidden. This fixes
a bug where if the controls were hidden while scrubbing, the timeline
would continue to handle touchmove events and scrub.

Bug: 810313
Change-Id: Iaa14e559e2f0b077df0d50043bb148bfb195a7a1
Reviewed-on: https://chromium-review.googlesource.com/912113Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537362}

To correctly implement poisson process sampling, we occasionally have to take
multiple samples from a single allocation. Since the memlog stream format does
not support a "count" or "weight" parameter, use "sz" as a proxy.

Bug: 810748
Change-Id: Ie87be75b0915afd5d032943f8a42cb5a190ce6e5
Reviewed-on: https://chromium-review.googlesource.com/922982Reviewed-by: Primiano Tucci <primiano@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537361}

In some cases, and on user's machines per bug reports, writev() performs
a short write. The child process receives an invalid profile and tabs
fail to launch. This switches to using a sequence of write() calls to
send the buffer length, and then send the buffer in a loop.

Bug: 801889
Change-Id: Ib1f4c57c61d3ce68b875b347de480f514100d3c2
Reviewed-on: https://chromium-review.googlesource.com/920765Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Greg Kerr <kerrnel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537360}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=paulmeyer@chromium.org

Change-Id: I0151100128e83c9746375ad898dac8bfc1a89e0e
Reviewed-on: https://chromium-review.googlesource.com/923345Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537359}

Parallel download system currently can't determine if the last slice is
finished, and always sends a new request after the last byte during
resumption, which may be out of range request if the last piece is
finished before other pieces. Servers must send HTTP 416 to make the
download complete or the download will fail.

This CL updates the database schema for parallel download slices table,
and uses the new column data to determine the actual file length
during resumption. So we don't need to send out of range request, which
is unneccessary and rely on server's good behavior.


Bug: 766737
Change-Id: I6e864dd3e01e511c0b770facc1c452a50e6c913c
Reviewed-on: https://chromium-review.googlesource.com/910688
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537358}

There is no unit test for tapping OK and Cancel buttons, because
it's something that is very hard to test in unit test (buttons are
not tappable unless the UI got synchronized).

UI mock: https://docs.google.com/presentation/d/1GzbAoJrpW9IAQF78afh5SZLWJWErNcC67t_ctujjEus/edit#slide=id.g2b7a689b42_0_196

Bug: 791806
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ic291ef5db83eaea4220ff1ed3f9501020de7389f
Reviewed-on: https://chromium-review.googlesource.com/919492Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537357}

This attempts to address crashes where the GPU process is hanging trying
to contact launchservicesd. It attempts to address these crashes by
allowing access to the lsdb.mapdb launchservices endpoint, which exposes
less attack surface than the full launchservicesd.

Bug: 812228
Change-Id: I1f44bad960d1d07fda622a4d5ad957b281c96792
Reviewed-on: https://chromium-review.googlesource.com/923126Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Greg Kerr <kerrnel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537356}

We don't need to do user-friendly stuff like:
* configure repositories or sources
* map NSS libraries for repo

This was copied from Chrome, but the .deb is just a packaging mechanism
for us.

Bug: 714465
Change-Id: I21cdaebbc5cf420427b4b912812f8197d18ff5a7
Reviewed-on: https://chromium-review.googlesource.com/923288Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537355}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=tdresser@chromium.org

Change-Id: Ic062c1ef20684790628223113ee62e577b374e9e
Reviewed-on: https://chromium-review.googlesource.com/924166Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537354}

These do not need base::ResetAndReturn, use std::move(callack).Run()
instead.

Change-Id: Ifa90ffffcae8e64fd8cced276e482b3ecf21d6a9
Bug: 812717
Reviewed-on: https://chromium-review.googlesource.com/920645Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537353}

Apparently a line like:

// foo

in the filter file results in all the other lines of the filter file
being ignored. This meant ash_unittests --mash on the bots wasn't
running any tests. Fixing the line shows a bunch of new tests are
failing. I've added them to the end and file a bug to recategorize
them.

I'll fix the bug in the filter file parsing separately.

BUG=813115
TEST=test only changes

Change-Id: If27f6e0738c4571c60e16bf87db6ba5cfac5cea3
Reviewed-on: https://chromium-review.googlesource.com/924270Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537352}

A main thread compositable animation means that this animation should
be composited such as an opacity or 2d transform, but it is not due to
certain check such as
RuntimeEnabledFeatures::TurnOff2DAndOpacityCompositorAnimationsEnabled
which is designed to be used for an experiment described in
crbug.com/754471.

Currently our logic is:
1. Check if the effect (such as opacity) can start on compositor or not
2. If 1 is true, and the target element is not paint into its own
   backing + the target element is not a SVG, then it is a main thread
   compositable animation.

This logic is over complicated. We should really just check whether the
run time flag is enabled or not. So this CL simplifies it. We already have
unit test in CompositorAnimationsTest to ensure that this change is
fine.

Bug: 781305
Change-Id: I8f9a1d82fa60eea79018c6cf777a1b45bd565022
Reviewed-on: https://chromium-review.googlesource.com/919316
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537351}

Exposes a getter and setter for focus_source_ on OmniboxEditModel and
uses them directly to track the focus source (omnibox or fakebox),
instead of relying on a workaround for Linux and using caret visibility
as a proxy.

Bug: 807600
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I6e23c77ca7c8cac39e07cc45c351b076a9183d1c
Reviewed-on: https://chromium-review.googlesource.com/894325
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537350}

It won't be necessary to call base::ResetAndReturn. Use std::move
to Run() those closures instead.

Bug: 812717
Change-Id: Ie8956bfcb23e3411025352d4714a9c928c0869fe
Reviewed-on: https://chromium-review.googlesource.com/920742
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537349}

In pre-DICE, the sync confirmation dialog was always shown after the
accounts were added to the Gaia cookies. This took several seconds
allowing the sync engine to initialize and check whether sync was
allowed for the given account.

When DICE enabled, the sync confirmation dialog should only be shown
after sync has been initialized or failed to be initialized. This allows
us to make sure that the policy to enable or disable sync for the given
account is checked before displaying the sync confirmation dialog.

BUG = 812546

Change-Id: Ic414cd8eb5a810a1ff0827526361b10f8e76210b
Reviewed-on: https://chromium-review.googlesource.com/921741Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Nicolas Zea <zea@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537348}

This also converts these enums from integer types to enum types so that
we can monitor them more easily.

Change-Id: I86ad00dea619787afb90046d80a12052586091b4
Reviewed-on: https://chromium-review.googlesource.com/922916
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537347}

This CL wires the Tab Grid into MainController.

The TabGridCoordinator is the MainCoordinator in this case (it creates and assigns the
root view controller for the app).

The TabGridViewController adopts the ViewControllerSwapping
protocol to show a tab switcher or a BVC. Since the TabGridViewController is itself the
view controller for the tab switcher when the tab grid is enabled, showing the tab switcher
is a no-op if a BVC isn't shown. The other presentation logic is lifted from
MainPresentingViewController.

To make that a bit cleaner, this CL factors bvc_container_view_controller into its own file.

The new TabGridAdaptor object, created and owned by the TabGridCoordinator, is the object
that exposes the TabSwitcher protocol. Future CLs will add hooks for it into the tab grid
controller and coordinator, which will be opaque to MainController.

As another small cleanup, the 'tabSwitcherController' ivar in MainController is renamed to
'tabSwitcher', since it's no longer necessarily a UIViewController. MainCoordinator also
separates its view controller from its view controller swapper, since in the tab grid
coordinator subclass those aren't the same thing.

The TabGridCoordinator unit tests are largely cloned from MainPresentingViewController's
unit tests, since their APIs are (at this stage) essentially the same.

Bug: 804533, 804531
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ia39101fc384100ca9c1ea9c1f7b08bc7e08b70e0
Reviewed-on: https://chromium-review.googlesource.com/917671
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537346}

A lot of classes in the glue depend on the
WebViewChromiumFactoryProvider because they need to post tasks to the UI
thread.
In this CL we move that task-posting functionality into
WebViewChromiumRunQueue to allow glue classes (including classes shared
between the webkit glue and the support library glue) to depend on
WebViewChromiumRunQueue instead of WebViewChromiumFactoryProvider.

We're leaving the original methods in WebViewChromiumFactoryProvider for
now to avoid having to change all callers at the same time.

Bug: 813089
Change-Id: I5f01179b1917df9aaa345f53f2292bcab8238368
Reviewed-on: https://chromium-review.googlesource.com/924184Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Gustav Sennton <gsennton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537345}

Shadowed variables can make code harder to read. Don't support them
in the content layer.

BUG=794619

This CL was uploaded by git cl split.

R=csharrison@chromium.org

Change-Id: Ia68095876eb2a6de4337cee243c0ae5b4c93ff8c
Reviewed-on: https://chromium-review.googlesource.com/924171
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537344}

Bug: 766233
Change-Id: I0af9b95727cd334af60f6e50904a9d04339bd7da
Reviewed-on: https://chromium-review.googlesource.com/923181Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537343}

Adds simNfcScanUntilVrEntered, which in most cases, replaces simNfcScan.
This is to deal with flakiness that stems from VrCore thinking that it's
still in VR from a previous test and nooping when it receives an NFC
scan in a following test.

Bug: 736527, 812306
Change-Id: If7b135b99df03c463f5b393bfbe6290e06d0ee4e
Reviewed-on: https://chromium-review.googlesource.com/923099Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537342}

This is more prep for Mac support. The current root is a WindowElement which is
backed by aura::Window.

Bug: 769352
Change-Id: Ie7e05fb528f9f54fc07bc5ce96397715e0e34f1e
Reviewed-on: https://chromium-review.googlesource.com/876307
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537341}

Also a couple of other places where ComputedStyle could be made
immutable.

Bug: 813068
Change-Id: I7cebac7951adbf65dbb057ef7b75d4ddab62e90c
Reviewed-on: https://chromium-review.googlesource.com/924145Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537340}

A proposal to allow the renderer to notify the browser of frame submission,
along with RenderFrameMetadata.

This change adds cc::RenderFrameObserver which LayerTreeHostImpl can notify of frame submission.
This change adds content::RenderFrameObserverImpl which implements the above. RenderWidget sets this on the LTHI.
MainThreadFrameObserver has been updated to enable observing.
NonBlockingEventBrowserTest.StartTouch has been updated to make use of this.

TEST=NonBlockingEventBrowserTest.StartTouch

Bug: 785013
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ic01e81331b34119a08488778f5dbe0c86a1775a3
Reviewed-on: https://chromium-review.googlesource.com/886655
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537339}

The test was disabled a year and a half ago due to flakiness. I cannot
reproduce it anymore.

BUG=376668

Change-Id: I7b6c99187f9ce53af2252dfe95e0b68da322af98
Reviewed-on: https://chromium-review.googlesource.com/922341Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537338}

This code is not used anymore.

Bug: 810049
Change-Id: I029652468ec67d8b238a89e25b8cb9193435b4dd
Reviewed-on: https://chromium-review.googlesource.com/909289
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537337}

Simply moving the files, no structural change

BUG=803135

Change-Id: I2c986f07eae2fef2bd316cda512054c27c01758c
Reviewed-on: https://chromium-review.googlesource.com/920643Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537336}

Bug: 813068
Change-Id: Ie5e3b8ccafd801575a5f886f1902abc547d9bacc
Reviewed-on: https://chromium-review.googlesource.com/923983Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537335}

BUG=813098
TBR=editing-dev

Change-Id: I9005cfc1cf4011ee0b424cb7f06270786115a386
Reviewed-on: https://chromium-review.googlesource.com/924221Reviewed-by: Thiemo Nagel <tnagel@chromium.org>
Commit-Queue: Thiemo Nagel <tnagel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537334}