GitLab

This is not ready to be used.

Bug: 771740
Change-Id: Ia54361b4985711729b693ab13dce959924298cdf
Reviewed-on: https://chromium-review.googlesource.com/701395Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: ccameron chromium <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506530}

Bug: 764125
Change-Id: Id90db21dd9333565bee94da935df90639be082c6
Reviewed-on: https://chromium-review.googlesource.com/699567
Commit-Queue: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506529}

As a result of
https://chromium-review.googlesource.com/c/chromium/src/+/670359
the values of SHOW_SEARCH_ENGINE_PAGE in FirstRunActivity#mFreProperties and
FirstRunFlowSequencer#shouldShowSearchEnginePage() are guaranteed to
be the same.

Bug=755646

Change-Id: I8a0eef268f34319af3c1129aec8066bee214582d
Reviewed-on: https://chromium-review.googlesource.com/700426
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506528}

Bug: 
Change-Id: Ib77d051ef0813cd63eafd92b578919f46982d26b
Reviewed-on: https://chromium-review.googlesource.com/700992Reviewed-by: Chris Sharp <csharp@chromium.org>
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506527}

Update README for errorprone and add owners. Use a single jar to make
maintenance easier and to pave the way to updates in the future.

BUG=383646

Change-Id: Ib9e2900141baab73515c957bb274b7568ef3102a
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/700856
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506526}

ResourceBundle became ui::ResourceBundle in r72038 but many callers
still refer to it without the namespace.

Change-Id: Id63635507b65d3d6ffe1fa3a779e189969030b11
Reviewed-on: https://chromium-review.googlesource.com/696138Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506525}

Introduce NavigatorAutomationInformation interface
that indicates if navigator is controlled by automation.
It is guarded by RuntimeEnabled and exists only if AutomationControlled feature is set.
https://w3c.github.io/webdriver/webdriver-spec.html#dom-navigatorautomationinformation

Bug: 723900
Change-Id: If54295456a24fe8c86958c037263939ba3e44cb7
Reviewed-on: https://chromium-review.googlesource.com/665978
Commit-Queue: Sergey Shekyan <shekyan@gmail.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506524}

I only verified one setting of a compile time boolean,
breaking the code when it had the other setting.

R=servolk@chromium.org, xhwang@chromium.org

Bug: 771166
Change-Id: Id22d6dcfaed6e2ffb247000afd2b968756c05b0f
Reviewed-on: https://chromium-review.googlesource.com/699056Reviewed-by: Sergey Volk <servolk@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Doug Steedman <dougsteed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506523}

This is not a complete set of new baselines.  It is based on
pattern-matching text diffs from try bot results based on two
heuristics:

1. For tests that dump the layer tree (i.e., those that output
internal.layerTreeAsText(document)), there is an expected diff in
the layer tree output of this format:

   "layers": [
     {
       "name": "LayoutView #document",
+      "bounds": [800, 600],
+      "backgroundColor": "#FFFFFF"
+    },
+    {
+      "name": "Scrolling Layer",
+      "bounds": [785, 600],
+      "drawsContent": false
+    },
+    {
+      "name": "Scrolling Contents Layer",
       "bounds": [785, 2513],
       "contentsOpaque": true,
       "backgroundColor": "#FFFFFF",

2. For tests that scroll the top-level FrameView and then dump the
layout tree (the default behavior), we expect the frame-level scroll
to be reflected in the positions of all layers; for example:

 layer at (0,0) size 800x600 scrollX 1255.00 scrollY 1023.00 scrollWidth 2055 scrollHeight 2063
   LayoutView at (0,0) size 800x600
-layer at (0,0) size 800x2063 backgroundClip at (0,0) size 800x600 clip at (0,0) size 800x600
+layer at (-1255,-1023) size 800x2063 backgroundClip at (0,0) size 800x600 clip at (0,0) size 800x600
   LayoutBlockFlow {HTML} at (0,0) size 800x2063
     LayoutBlockFlow {BODY} at (8,8) size 784x2047
       LayoutBlockFlow {DIV} at (0,0) size 2047x2047
-layer at (8,8) size 784x0
+layer at (-1247,-1015) size 784x0
   LayoutBlockFlow {DIV} at (0,0) size 784x0
 scrolled to 1255,1023

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

Memory allocated here is expected to leak.

Bug: 770463
Change-Id: Iaa741c9753e018fe76d7e008d40d42a79e93c6fa
Reviewed-on: https://chromium-review.googlesource.com/701416Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506521}

Make it clear that Revoke() must be called after Consume(), which is
what the current DCEHCK in dtor checks. If an extension does not need to
be revoked, use ConsumePermanently().

BUG=510604
TEST=No functionality change

Change-Id: Ifee995ffdfc608e4ccc40bbbb4096511c561237a
Reviewed-on: https://chromium-review.googlesource.com/701274
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506520}

During the refactor to make downloads a foreground service on all
versions of Android, a problem arose where Chrome crashes when
canceling a file that is downloading. This CL fixes that issue.

Bug: 771122,747563
Change-Id: Idaa2377ef06df1d30b6947e92b6743ad5e4b16c2
Reviewed-on: https://chromium-review.googlesource.com/700774Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Joy Ming <jming@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506519}

https://chromium.googlesource.com/catapult.git/+log/d0b91b8f3a17..8894309be5ce

$ git log d0b91b8f3..8894309be --date=short --no-merges --format='%ad %ae %s'
2017-10-03 wkorman Export external image element ids and urls.
2017-10-04 simonhatch Dashboard - Add support for tracing_perftests.
2017-10-04 wkorman Don't emit empty style tags.

Created with:
  roll-dep src/third_party/catapult


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I445f509d79b4d2f82ab922cb919f330b871c1852
Reviewed-on: https://chromium-review.googlesource.com/700979
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506518}

Command line flags are initiated by instrumentation tests' class
runner. One should avoid calling CommandLine.init(null) manually
in tests after native command line starts.

Bug: 771205
Change-Id: I1e6d026a45c60eb81ce0860971fa2da44ab0285b
Reviewed-on: https://chromium-review.googlesource.com/698351
Commit-Queue: Yoland Yan <yolandyan@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506517}

This check is triggering on data types that are erroneusly written to
the local sync db in the first place althoug they don't cause further
processing errors.

This is a fix for users with already messed dbs. Further fix will
make sure commit-only entries are not serialized to the db at all.

BUG=771598

Change-Id: Ifd7e5c5d07e5ab061cbb2cc1d7bbf54210568304
Reviewed-on: https://chromium-review.googlesource.com/701054
Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506516}

SSLErrorHandler ignores updates to SSL Error Assistant proto if the
version_id of the new updated proto is not greater than the version_id
of the current proto. The test helper was using INT_MAX for version_id
of the updated proto. This meant that the proto was only being set once
and subsequent updates were ignored. Also, the value of
os_reports_captive_portal_for_testing_ wasn't reset properly in tests.

Bug: 642993
Change-Id: I4b021e5973ae6d4e7d95e61d55d7b117e1c2824d
Reviewed-on: https://chromium-review.googlesource.com/699425
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506515}

Pdf compositor service is a utility service that uses skia to render
and generate pdf document. Thus it needs to access local font system.
On Linux, it needs 'uname' to get user agent. So, on Windows and Mac,
it resembles ppapi process in term of sandbox policy. On Linux, it is
closer to utility process's sandbox requirements. To make its
requirements clear, we create a new service sandbox type for it, and
apply appropriate policy on different platforms.

TBR=jam@chromium.org
BUG=455764

Change-Id: I7c7aeb40e5e0b09fe29887532c06d2abc04969d6
Reviewed-on: https://chromium-review.googlesource.com/695781
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506514}

It was marked as flaky in 2011. Things have changed since then.

Bug: 84729
Change-Id: I638f9c26e9636dff8f27903df5e64ff911d10a03
Reviewed-on: https://chromium-review.googlesource.com/700954Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506513}

https://skia.googlesource.com/skia.git/+log/fa8c08044989..0078e912718c

$ git log fa8c08044..0078e9127 --date=short --no-merges --format='%ad %ae %s'
2017-10-04 angle-deps-roller Roll skia/third_party/externals/angle2/ a99ed554c..baf5d9458 (1 commit)
2017-10-04 csmartdalton Rename GrOpList::reset to endFlush
2017-10-03 benjaminwagner Add more detail to Swarming bot doc.

Created with:
  roll-dep src/third_party/skia


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


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;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=scroggo@chromium.org

Change-Id: I0516a7cca7bd2500a1425be30de1e82ebd15d74c
Reviewed-on: https://chromium-review.googlesource.com/700755Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506512}

This is a reland of 419b66b5

Original change's description:
> Fix behavior around closed message ports.
>
> Connect a closed message port to a dangling message pipe to make sure
> messages posted to the port end up getting lost, even after the message
> port is transferred to a different process.
>
> Bug: 673526
> Change-Id: I95467bf5c3e1af316c8781bcca6dfdda29936fe8
> Reviewed-on: https://chromium-review.googlesource.com/690981
> Reviewed-by: Jeremy Roman <jbroman@chromium.org>
> Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#505760} Conflicts:

TBR=jbroman@chromium.org

Bug: 673526
Change-Id: Iafdcc3e8891e80c120d270f6f04bb79a55092067
Reviewed-on: https://chromium-review.googlesource.com/700323Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506511}

When updating icon->page URL mappings, the code has historically
associated icons to both the original page URL as well as the
fragment-stripped page URL (for page URLs that contain a fragment/ref).

This can cause "orphan" entries in the favicon database, i.e. mappings
that don't have a corresponding history entry (because the page URL
without a fragment was never actually visited). This means the
history expirer will never take care of cleaning them up, leaking
until the user clears all history.

The original logic was introduced to fix crbug.com/498618 which is no
longer reproducible even after this patch.

With recent improvements in client-side redirect handling (e.g.
https://chromium-review.googlesource.com/569760 or
https://chromium-review.googlesource.com/595977), it is conceivable
that these historical heuristics are no longer needed. Since this is
hard to prove, we put the new behavior behind a feature than can be
experimented via Chrome variations.

Bug: 746268
Change-Id: Ieefb0fdb175d8858f1055af2dcc54df2e6f00a9a
Reviewed-on: https://chromium-review.googlesource.com/649691
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506510}

This is a superficial fix by checking |this.webview_.contentWindow|,
but it's unknown why it is null.

Two different scenarios were observed:
1) |Authenticator.onContentLoad_| is called with a non-null
contentWindow (expected).
2) |Authenticator.onContentLoad_| is called with a null contentWindow,
and is immediately called a second time with a non-null
contentWindow. However, the first call already results in a failure
and the page fails to load. This patch will temporarily fix this case.

It's never observed that |Authenticator.onContentLoad_| is called only
once with a null contentWindow . If that case happens, then this CL
will make the page load successfully but without a |postMessage| call,
and create additional issues.

Bug: 711486
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ieec4ac33673df9b393792ec82ea034546b165b0f
Reviewed-on: https://chromium-review.googlesource.com/700034
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506509}

We have not shipped Windows Ash for years. There is a 1:1 mapping
between "use_ash" and "chromeos", so consolidate them.

TBR=oshima@chromium.org for theme_resources.grd

Bug: 673826
Test: compiles, bots
Change-Id: If76122c1089cde2ec2b7d8822a4ca0adde25e5f3
Reviewed-on: https://chromium-review.googlesource.com/699663Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506508}

Bug: 771620
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I2dc798906f16528b4e56b9f7c6bb7869327afb54
Reviewed-on: https://chromium-review.googlesource.com/700734Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Walter Korman <wkorman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506507}

TBR=

Bug: 
Change-Id: I2e837413ced0b2befa77e6c8cff4b548cc574198
Reviewed-on: https://chromium-review.googlesource.com/685586
Commit-Queue: Mike Reed <reed@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Reviewed-by: Ben Wagner <bungeman@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506506}

This CL adds a VrDisplayHost with bindings to the renderer to route
requests for presentation through the browser.

(The next CL will move the focus-checking code from VrShellDelegate into
the new VRDisplayHost)

Bug: 768923
Change-Id: I88ae9797ebe8cbf182b117c2cd07cf91d8d09361
Reviewed-on: https://chromium-review.googlesource.com/692505
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506505}

Bug: 764371
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I39faede4afe5fd094805d35dbccf847ac8d6c2b7
Reviewed-on: https://chromium-review.googlesource.com/692595Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Thanh Le <thanhdle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506504}

Decouple overrides for MATCHES_PREVIOUS_LANGUAGE and LANGUAGE_DISABLED_BY_AUTO_BLACKLIST event types.
This will allow to run experiments on heuristics override indepedently for each case.

Bug: 769767
Change-Id: I24fffee57f0718575999b0ae88028be9dc19b895
Reviewed-on: https://chromium-review.googlesource.com/690437Reviewed-by: Rachel Blum <groby@chromium.org>
Commit-Queue: Philippe Hamel <hamelphi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506503}

TBR=brettw@chromium.org,inferno@chromium.org

Bug: 771718, 759794
Change-Id: I1fc3ab8b054ce6eeee24d0c1c0599be216b2e386
Reviewed-on: https://chromium-review.googlesource.com/700974Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506502}

This should eliminate a synchronous IPC.

Also change location of Mac-specific GPU back-pressure code.

BUG=770924

Change-Id: Id44286f3359662ec3122b1e421d22f860ea24463
Reviewed-on: https://chromium-review.googlesource.com/696666Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506501}

Added AudioOutputStreamFuchsia which implemented audio output using
Fuchsia's media_client library. Also updated AudioManagerFuchsia to
enumerate output devices and create AudioOutputStream.

Bug: 737802
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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
Change-Id: I344ed5ad885d602574dd03ad31e85d7b76e0c2b8
Reviewed-on: https://chromium-review.googlesource.com/690622
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506500}

Instead of using setTimeout to hope for a style recalculation,
we now read offsetTop to force a style recalculation.


Bug: 770362
Change-Id: Ic4918cd336aef56641e483ce2ae8d31ceb29acc9
Reviewed-on: https://chromium-review.googlesource.com/700154Reviewed-by: Ali Juma <ajuma@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506499}

 * Update content description for expand button
 * Update promo dialog text when accessibility is enabled

BUG=767738

Change-Id: I0d33304803855e6fe894f26a83d10d9c3c361244
Reviewed-on: https://chromium-review.googlesource.com/699916Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506498}

animations/unanimated-style.html was using setTimout(0) to wait for the
initial style calculations
before starting the animation. This isn't a reliable method.

We now force style recalc explicitly by reading an element's offsetTop.

BUG=770362

Change-Id: Icf518b3a43b51d854de81cc2fab371922e271e16
Reviewed-on: https://chromium-review.googlesource.com/699974Reviewed-by: Ali Juma <ajuma@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506497}

The test would previously fail if a rAF callback occurred 0.3s later
than anticipated.

We increase the animation duration, so that the animation will still
be in progress if the callback occurs later that anticipated.

The entry in TestExpectations is no longer needed.

BUG=248938

Change-Id: Ida03745d18bd5a8ac4d454fc0e3fbdae5254d20a
Reviewed-on: https://chromium-review.googlesource.com/699954Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506496}

This reduces the size of the extra large backing store class, and leads
towards a smaller class in the future as other classes can now call the
appropriate leveldb operations.

R: cmumford@chromium.org, pwnall@chromium.org
Bug: 725565
Change-Id: I29e7c72970b47801a51db4548f9e0a1b3ae26d4b
Reviewed-on: https://chromium-review.googlesource.com/693382Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Reviewed-by: Chris Mumford <cmumford@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506495}

TBR=palmer@chromium.org

Bug: 
Change-Id: I14ff5597d1482fe56836ba49dcee6f6755c303c5
Reviewed-on: https://chromium-review.googlesource.com/673127Reviewed-by: Lucas Garron <lgarron@chromium.org>
Commit-Queue: Lucas Garron <lgarron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506494}

Bug: 771381
Change-Id: I42a1b5c2d691e9973f21ac0de8fc441aa9fe3e21
Reviewed-on: https://chromium-review.googlesource.com/699940Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506493}

This is a necessary preparatory step for optimizing the MD Extensions
page with polymer-bundler.

 Side benefits of this change:
 - No need for the repeated "resources/md_extensions" prefix on every file's
   path declaration in the grd file.
 - Faster build times when a file is touched (no longer need to rebuild
   the gigantic browser_resources.pak)
 - No longer need to call source->AddResourcePath() repeatedly in
   extensions_ui.cc.

Also moved two HTML files that were misplaced in the old Extensions folder
even though they are only used in the new MD version.

Bug: 764126
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ie9b13ed4f46fa14f27d9280eca40c9cd79a6d4b4
Reviewed-on: https://chromium-review.googlesource.com/696670
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506492}

Define the mojom::InputDeviceInfo. Simply replace the old
native InputDeviceInfo. Make sure all the existed test cases pass.

In next CL we'll do the mojofication. The InputServiceProxy will
be removed then.

BUG=767309

Change-Id: Ic307a794592e74d73fb016c56ec24c027441c41b
Reviewed-on: https://chromium-review.googlesource.com/676944Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Ke He <ke.he@intel.com>
Cr-Commit-Position: refs/heads/master@{#506491}