GitLab

This helps controls scripts get a better idea of the current virtual
time.

Bug: 
Change-Id: I39433f2790cdc51c14a3c02736c9320b0bce7c0a
Reviewed-on: https://chromium-review.googlesource.com/702374Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506789}

This will allow devtools protocol users to distinguish between forms that
use GET and POST.

Bug: 
Change-Id: Id27f36cb675aaea02434a76eae492faac320f01e
Reviewed-on: https://chromium-review.googlesource.com/700518Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506788}

Headless users may want to decode captured traffic.

Bug: 767532
Change-Id: Ied7fa3ec4fb771f845d9c38eb2a476f2e5a3b018
Reviewed-on: https://chromium-review.googlesource.com/677569
Commit-Queue: David Benjamin <davidben@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506787}

For some reason, the ThreadSafeRefCounted destructor was not
inlined in release builds. The end result was a completely empty
function, that was called in many many places.

This tells the compiler that, for release build, the destructor
is inlined and doesn't do anything. This tiny patch reduces the
final (compressed) size of the following Android APKs:

  - Chrome.apk       -60 KiB  (from 45 MiB)
  - Monochrone.apk  -152 KiB  (from 69 MiB)

Note that the destructor is kept non-inlined for debug builds,
since it must perform relevant debug checks.

R=tzik@chromium.org,thakis@chromium.org,dcheng@chromium.org,agrieves@chromium.org
BUG=NONE

Change-Id: I45c9e87851a3c71861034bde8906b59d1033c455
Reviewed-on: https://chromium-review.googlesource.com/702301Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506786}

After a successful StopForRestart(), if Restart() fails, the source
should return to the previous state, which is STOPPED_FOR_RESTART,
instead of being stopped for good.

Bug: 763319
Change-Id: I907c320d0d4664d3b35fe89d141eb936381e78c7
Reviewed-on: https://chromium-review.googlesource.com/695306
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506785}

Adds metrics around advertisement registration/unregistration,
scanning, creating a GATT connection, and the StartNotify operation.

These metrics are being created in addition to existing similar
Bluetooth metrics in order to gauge Tether's stability as a client
versus Bluetooth as a whole.

Bug: 
Change-Id: Idf719394e4193591230cc765d48a8ceb0a0f4b88
Reviewed-on: https://chromium-review.googlesource.com/701373Reviewed-by: Tim Song <tengs@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506784}

This provides a toolchain target for aarch64 Fuchsia and fixes a linux
assumption in the generic compiler setup. The Fuchsia SDK provides a
sysroot for aarch64 and the clang toolchain used by Chromium
understands the aarch64-fuchsia target already.

Bug: 772031
Change-Id: I6537b53d598afd2a0185870495261be8bc395c87
Reviewed-on: https://chromium-review.googlesource.com/701932
Commit-Queue: James Robinson <jamesr@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506783}

Bug: 763181
Change-Id: I869ee1e72bddad2bf6b5aaf11c5480ae21a28da3
Reviewed-on: https://chromium-review.googlesource.com/701928Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: min c <minch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506782}

Most notably we would like to have this new lint for Blink internal APIs
in external/wpt: https://github.com/w3c/web-platform-tests/pull/7544

Bug: 749879
Change-Id: Ia1b2a1832b53e98d0c3204948a003a88d24dfff0
Reviewed-on: https://chromium-review.googlesource.com/702534
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506781}

This change routes HitTestRegionList objects received by
CompositorFrameSinkSupport to the HitTestManager.

The HitTestAggregator will query the HitTestManager for the
active HitTestRegionLists when aggregating the data.

HitTestManager also manages the lifetime of HitTestRegionList
objects by deleting old objects when surfaces are discarded
and deleting objects that correspond to older frames when
a new surface is activated.

This change also modifies HitTestAggregator memory management
so that new memory is allocated as needed while aggregating
HitTestRegionList data.

Bug: 732399
Change-Id: Iaedec31a34f04446a539acd10d77c6fe18034d44
Reviewed-on: https://chromium-review.googlesource.com/650220
Commit-Queue: Gary Klassen <gklassen@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Ria Jiang <riajiang@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506780}

For more on JUnit4 migration, please check
src/testing/android/docs/junit4.md

Bug: 640116
Change-Id: I6a1857ab3322176c03256fba003f5a1677b5899e
Reviewed-on: https://chromium-review.googlesource.com/701639Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Commit-Queue: Yoland Yan <yolandyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506779}

This reverts commit 73c5accd.

Reason for revert: Breaks the Win 10 GPU FYI bots that can't find swarming bots with the required configuration anymore.

Original change's description:
> Specify Win/NVIDIA GPU bots driver version.
> 
> Explicitly specifying the GPU driver version in the config will allow
> us to safely test new driver versions. Because the tests will pick
> machines of a particular driver version specified in the json, we
> can ask infra to upgrade a few machines, then run a try job using the
> new driver version.
> 
> This modifies the generate script to allow use of wildcards in test
> dimension set specifiers. Wildcards are only supported as the last
> character in the dimension. This allows us to more easily match
> ranges of driver versions.
> 
> The current NVIDIA driver version used by the bots is 372.54.
> 
> R=​kbr@chromium.org
> BUG=771654
> 
> 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: I5875b9e91fbe8d2d626a8af20005161bc3f082bb
> Reviewed-on: https://chromium-review.googlesource.com/699761
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Commit-Queue: Jamie Madill <jmadill@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#506600}

TBR=jmadill@chromium.org,kbr@chromium.org

Change-Id: Id8c6f60074994e7a7ae9a62a9e0f6658ba43fc6d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 771654
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
Reviewed-on: https://chromium-review.googlesource.com/702734Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506778}

BUG=none
TEST=none

Change-Id: I721fd9c401a987611773025349bea391928ca810
Reviewed-on: https://chromium-review.googlesource.com/693821
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506777}

Instead call SessionController::RequestSignOut which does
the same thing.

Bug: 758365
Change-Id: I138b58a05a10a4cdc748896746a5acf14f9bb980
Reviewed-on: https://chromium-review.googlesource.com/699430
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506776}

The userAgent strings associated with some emulated mobile devices
contain substring "%s", which should be replaced with Chrome version.

Bug: chromedriver:1883
Change-Id: I475a9a20e72008956bc201b3677cb60f6632e57c
Reviewed-on: https://chromium-review.googlesource.com/689966
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506775}

Bug: 761362
Change-Id: Ib0cbc54e99bcde0be88317a87eeb903136128978
Reviewed-on: https://chromium-review.googlesource.com/691662Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506774}

Previously we have a dedicated detector to detect network idleness signal and
send it to services/resource_coordinator, however, it uses a timer, thus it
can't handle cases like, if a task is being processed for a long time, network
requests won't be able to be fired, thus when the task is finished processing
the network idleness signal will be fired before network requests are fired,
which results in inaccurate network idleness signal.

So, in this patch, we excluded task processing time in network idle time
accumulation, and merged Performance Monitor life cycle report into the current
detector.

Minor: renamed kNetworkIdle to kNetworkAlmostIdle, renamed class/file name to
IdlenessDetector.

BUG=730098, 749789

Change-Id: Ied003129cd5ddf7c1ebb93019723e11e9a31be04
Reviewed-on: https://chromium-review.googlesource.com/664094
Commit-Queue: lpy <lpy@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Zhen Wang <zhenw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506773}

Adds UKM to report the duration in millisecond from when a tab is backgrounded
to it is closed or foregrounded.

BUG=753486

Change-Id: I995b4002c80c1eb91f3ed36556e23c5b06183edf
Reviewed-on: https://chromium-review.googlesource.com/654144
Commit-Queue: lpy <lpy@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506772}

BUG=681511
R=mkwst@chromium.org

Change-Id: I351b28a09bfe09e5045ada5e228f8f0958a9eccb
Reviewed-on: https://chromium-review.googlesource.com/700264
Commit-Queue: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506771}

Chrome on iOS only uses a subset of skia (see ios/chrome/DEPS).
That subset does not include fonts rendering, so the dependency
on //third_party/freetype and //third_party/harfbuzz can be
removed.

Bug: none
Change-Id: Ie3adf4abab442428986eafe074da0447b169db4e
Reviewed-on: https://chromium-review.googlesource.com/697586Reviewed-by: Rohit Rao (ping after 24h) <rohitrao@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506770}

This CL adds ThreadUtils.runOnUiThread around call to
AccountManagerFacade.getNewAuthToken as this method should be invoked
on UI thread only.

Bug: 759023
Change-Id: I67c05084dca091ab1909549556211f84b8dec9c6
Reviewed-on: https://chromium-review.googlesource.com/702303Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506769}

This adds support for parsing APNG images by hooking into the
data_decoder service. webkit::WebImage API is extended to support
fetching the relevant animation data from blink's PNG decoder.

Bug: 750064, 719015
Change-Id: I7fb38643dce5d6e16eaaee2b6f74253ba70af20a
Reviewed-on: https://chromium-review.googlesource.com/679459
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506768}

The insecure content warning WebVR overlay is (virtually) unused, and
causing maintenance overhead. It will never ship, so we should just
remove it.

Bug: 771223
Change-Id: I852e5bed6954606b894955fce71942b5e19dc3f0
Reviewed-on: https://chromium-review.googlesource.com/698276
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506767}

https://skia.googlesource.com/skia.git/+log/3a9305383169..8d64ee779599

$ git log 3a9305383..8d64ee779 --date=short --no-merges --format='%ad %ae %s'
2017-10-04 bungeman Update SkBufferHead fRefCnt to std::atomic.

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: I053b4db1cabb725cbb6ae07441270e7c53ec1d96
Reviewed-on: https://chromium-review.googlesource.com/701672Reviewed-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@{#506766}

BUG=None
TEST=Ran cpplint.py to all files under the directories.

Change-Id: I91c5556b56c53ae4c66f6e288d3b6c37dea017ed
Reviewed-on: https://chromium-review.googlesource.com/702080Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506765}

Reworks the DownloadService's code to interpret DownloadItem states
better.  We have some unexpected states/transitions from DownloadItem to
DriverEntry that are causing our resumption/fail logic to get confused.
This brings over the concept if "done" and "can_resume" into the state
rectification logic.

TBR=sky@chromium.org

Bug: 769426
Change-Id: Iad7bc612a68421471ff4204e6a94d52eaea1b825
Reviewed-on: https://chromium-review.googlesource.com/699562
Commit-Queue: David Trainor <dtrainor@chromium.org>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506764}

There was a duplication of the source type checking. It may lead
errors when a type set will be changed for a language.

R=dpranke@chromium.org

Bug: None
Change-Id: Ieab8885899446e625cfe20c1650418a085b937ee
Reviewed-on: https://chromium-review.googlesource.com/702414Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506763}

This is to make sure future readers of that code don't make the same
mistake that we've done in the past.

Bug: 757398
Change-Id: Ie249e7b3ef22c8c0f8e69995a6adef463677e745
Reviewed-on: https://chromium-review.googlesource.com/701597Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506762}

Bug: 771987
Change-Id: If0293e9c73d575719544fbbdcb1f40fbf6df4962
Reviewed-on: https://chromium-review.googlesource.com/702057Reviewed-by: Sorin Jianu <sorin@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506761}

For more on JUnit4 migration, please check
src/testing/android/docs/junit4.md

Bug: 640116
Cq-Include-Trybots: master.tryserver.chromium.mac:mac_optional_gpu_tests_rel
Change-Id: I06ab6c5d14bdc382b294482d6a7b3cec497117e0
Reviewed-on: https://chromium-review.googlesource.com/701363Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Yoland Yan <yolandyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506760}

This reverts commit 7e5cda7a.

Reason for revert:
The test is failing. See e.g.
https://build.chromium.org/p/chromium.fyi/builders/ClangToTLinux%20tester/builds/2976

Before re-enabling on the ToT Clang bots, please have the test enabled
and passing on regular buildbots, including the CQ.

This also removes the test from the Clang bots from the new chromium.clang waterfall.

Original change's description:
> Reland "Add libfuzzer_tests to chromium.fyi Clang ToT testers (w/ and w/o ASan) on Linux."
> 
> Bug: 764514
> 
> Original CL: https://chromium-review.googlesource.com/679619
> 
> R=​dpranke@chromium.org
> 
> Change-Id: I412ac11cbe2c73de9e7b724e2689a97144aad47e
> Reviewed-on: https://chromium-review.googlesource.com/688029
> Reviewed-by: Oliver Chang <ochang@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Commit-Queue: Max Moroz <mmoroz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#505167}

TBR=dpranke@chromium.org,ochang@chromium.org,mmoroz@chromium.org

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

Bug: 764514,765859
Change-Id: I7af22d752dfcc48c580a7a704d02b2b5a065da1b
Reviewed-on: https://chromium-review.googlesource.com/701424
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506759}

BUG=763529
TEST=none

Change-Id: I24969570d882c546994a60d29d34a73366bce047
Reviewed-on: https://chromium-review.googlesource.com/701472Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506758}

Bug: 755783
Change-Id: I2c9e36d26e91b592a41ce94c1a6618ca3bceaea6
Reviewed-on: https://chromium-review.googlesource.com/690750Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506757}

I never ended up needing it.

BUG=763529
TEST=none

Change-Id: I4690f87c1979f58c966bd8a5e7cda606616e2320
Reviewed-on: https://chromium-review.googlesource.com/701834Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506756}

It is desired to remain open so users can try out the features without
having to tray->accessibilty->details each time. Also modified
hover_highlight_view to support showing/removing checkmarks dynamically,
for this purpose (other details views just recreate the whole view).

Bug: 747473
Test: browser_tests TrayAccessibility.DetailMenuRemainsOpen
Change-Id: I1160c29baac2afc8dc8a25dee3a87415ccef1adf
Reviewed-on: https://chromium-review.googlesource.com/692680
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506755}

A previous commit (791fb7fd)
inadvertently
reverted 8564fcee that's required to fix
a downstream bot. Relanding it.

From the initial commit:

    This causes link issues with a "missing key method" for the orderfile
    bot. This is due to a virtual member function not marked as pure, yet
    not implemented.

Bug: 767836
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: Ifa8b02eaf19c7475882823499228974e2d75cd55
TBR: watk
Reviewed-on: https://chromium-review.googlesource.com/702395Reviewed-by: Matthew Cary <mattcary@chromium.org>
Commit-Queue: Benoit L <lizeb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506754}

This FYI bot was using the --isolate-extensions flag, which has been
removed after we shipped this mode in M56.  Switch its tests in
chromium.fyi.json to --site-per-process, which also brings them in
sync with how the layout tests already run on this bot, according to
/build/scripts/slave/recipe_modules/chromium_tests/chromium_fyi.py.

Bug: 417518
Change-Id: I668673b2192ce94f321dff91b8bbcfb9f31c6800
Reviewed-on: https://chromium-review.googlesource.com/701280Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506753}

Orignal CL: https://chromium-review.googlesource.com/667062
Revert CL: https://chromium-review.googlesource.com/687434

Revert occurred due to compile error under 64-bit MSVC, when
size_t is implicit casted to offset_t = uint32_t.

This CL fixes the error for reland.

Bug: 729154
Change-Id: I02b0ce37dd42843318cde0670bfd3ac7111b8284
Reviewed-on: https://chromium-review.googlesource.com/695827Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506752}

Previously we'd passed a resource id and a color callback when creating
a Text instance. Now that we've switched to databinding and have
resources for unit tests, this can be simplified to ease the use of
Text in tests.

Bug: None
Change-Id: I610d08a5e18091db03b640f453635f90e5d9f12a
Reviewed-on: https://chromium-review.googlesource.com/701802Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506751}

BUG=None
TEST=Ran cpplint.py to files under chromeos/dbus.

Change-Id: Id5ffb9b8dc986cb224df6ac630dc6b3871242572
Reviewed-on: https://chromium-review.googlesource.com/702135Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506750}