GitLab

Corrected documentation for attaching LayoutObjects to whitespace text
nodes after landing crrev.com/7c44da72

Bug: 756340
Change-Id: I1ed807b170f613f6b7b7dfed50b58b121af0b564
Reviewed-on: https://chromium-review.googlesource.com/766349Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516098}

changes:
move TriggerAccessibilityAlert from AccessibilityDelegate to
AccessibilityController. This is part of mash work aimed at removing
AccessibilityDelegate.

Bug: 618070
Test: covered by tests
Change-Id: Ic5c026df5a33516e135be5edf38f6fea4cf1d9dc
Reviewed-on: https://chromium-review.googlesource.com/764597
Commit-Queue: Qiang(Joe) Xu <warx@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516097}

- Promise.resolve -> Promise.then
- Promise.reject -> Promise.catch

R=dgozman@chromium.org

Bug: chromium:778796
Change-Id: Ieca9cb08f474a600752e8ae6520a6d93452cb084
Reviewed-on: https://chromium-review.googlesource.com/767008
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516096}

Tab metrics prefs should be registered by Chrome. Currently they live
in the metrics component itself, which isn't Chrome-specific.

The other prefs in the metrics component are related to metrics
collecting/uploading. Prefs needed for tracking arbitrary features via
metrics should be colocated with the classes that track them.

This change also ensures we don't register these prefs on Android,
where they aren't used.

Bug: 720131
Change-Id: Ibaca7241b4dc2d62a8c631fe15a7774cd6fe474c
Reviewed-on: https://chromium-review.googlesource.com/760402
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516095}

This is to assess if pushed responses with Vary header could be rejected
(if proportion is very-very low).  See public discussion at
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/5_aP_stqndw.

Also add unittests.

Bug: 554220
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I8c5c95fc12da056fed7f837c79419e969f991a35
Reviewed-on: https://chromium-review.googlesource.com/755093Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516094}

This CL switches the default sysroot from Jessie to Stretch.
There are no deps changes.  The libstdc++ requirement is not
affected because we do an in-tree build of libc++ instead.
The glibc requirement is also not changed because we don't
currently use any of the symbols from the newer version.

BUG=751812
R=dpranke@chromium.org,thestig@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.linux:linux_arm

Change-Id: I89da578852fe0f7bfd27ffc08fda99e3b4df239e
Reviewed-on: https://chromium-review.googlesource.com/598737Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516093}

When popup window, e.g. settings, in immersive fullscreen is with immersive
revealed, the top view inset should be 0 otherwise in the overview mode
it will clip extra part of the popup window.

Bug: 778840
Test: On emulator and device.
Change-Id: Id0c3ac949186101fe6dca201a133e3258cfa2454
Reviewed-on: https://chromium-review.googlesource.com/750078Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516092}

TBR=nednguyen@google.com, junov@chromium.org

Bug: 784540
Change-Id: Ie82891952ed92ca920d2e14c42b7bc1520068310
Reviewed-on: https://chromium-review.googlesource.com/767288Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516091}

This moves chromeos-daisy-rel and linux-chromeos-rel from 50%
experiments to full members of the CQ, and removes
chromeos_daisy_chromium_compile_only_ng and
linux_chromium_chromeos_rel_ng (which are on tryserver.chromium.linux)
from the CQ.

R=jbudorick@chromium.org
BUG=732531

Change-Id: I3d91014b8c1f4f1d9d91acb0f8816faa155813b3
Reviewed-on: https://chromium-review.googlesource.com/767042Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516090}

This CL removes the domain to origin scoped migration code added for
crbug.com/604612. The pref used for the migration is now cleared on
startup to ensure that dead data is not retained.

BUG=621398

Change-Id: I053091ae9e6e5f816a5e5ece84bd7f46882904fa
Reviewed-on: https://chromium-review.googlesource.com/765554Reviewed-by: Timothy Loh <timloh@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516089}

* Remove some of the leftover tamper detection code
* Add an explicit callback when a new client config is fetched
* Limit the use of mock config for only the tests where it is actually required
* Remove the deprecated mock call to the network quality estimator

Bug: 760294, 675761
Change-Id: Iaf8077e83bacca574aa6dea0ed9906f0d25d0176
Reviewed-on: https://chromium-review.googlesource.com/766072Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516088}

I discovered this because animation frames weren't being executed since the
test config wasn't properly replicated in the test_runner for secondary renderer.

Previously in the old test harness, this worked because DevTools was the
secondary window and LayoutTestDevToolsBindings observes the DevTools window and
implements RenderFrameCreated.

This includes a test that we previously couldn't migrate because rAF was never called.

Bug: 667560
Change-Id: I286f27af3e4b87ffff368f2284a9a3b373e9b269
Reviewed-on: https://chromium-review.googlesource.com/764853
Commit-Queue: Will Chen <chenwilliam@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516087}

Removed code duplication for these calls:
[self loadCompleteWithSuccess:NO forNavigation:navigation];
[self loadErrorInNativeView:error navigationContext:navigationContext];

Bug: None
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ie550a088fefb154c13bc0409eaf7772b1d14b4c4
Reviewed-on: https://chromium-review.googlesource.com/757823Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516086}

The FYI bot ran without any failures in browser_tests for the weekend.

BUG=755272,755328
TEST=test only change

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

Bug: 771643
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I7258834a228a67f0adae1496fb89ebe2ed29c3f8
Reviewed-on: https://chromium-review.googlesource.com/723859
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516084}

Needed for JS support for OpenVPN.ExtraHosts

Bug=742666
TEST=Manually tested using networkingPrivate

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: If0de0606074c6805311d9b299bdc5c0a3de91b19
Reviewed-on: https://chromium-review.googlesource.com/726884Reviewed-by: Kevin Cernekee <cernekee@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Matthew Wang <matthewmwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516083}

The test code for verifying the scaling of the FFT was totally
confused (and confusing).  Correct the code, and only use the promise
instead of both the promise and the completion event.

Bug: 783314
Test: Analyser/realtimeanalyser-fft-scaling.html
Change-Id: Iecc607205c1cd0ed6e76bfa7c627907238f6a46e
Reviewed-on: https://chromium-review.googlesource.com/761436Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516082}

Before this CL, windows (or tabs, panels, etc.) created by
chrome.windows.create API form a relationship that is almost,
but not quite, like an opener relationship:

1. Unlike in a true opener relationship, the 2 frames (opener and
   openee) can find each other, but only if they are still in the same
   process.  For example, if only 1 frame navigates cross-process,
   then the frames won't be able to find each other (for a specific
   example please see https://crbug.com/713888#c5).

2. Unlike in a true opener relationship, window.opener is not set
   (and consequently cannot be navigated by the openee).


After this CL, chrome.windows.create API forms a true opener
relationship *iff* the new parameter - setSelfAsOpener is used.
Otherwise, the newly opened window is created in a separate browsing
instance.  This is required for later restricting named frame lookup
to the current browsing instance (see https://crbug.com/718489).

The CL establishes a true opener relationship, by having
extensions::WindowsCreateFunction::Run pass an opener (a
RenderFrameHost*) into chrome::NavigateParams, rather than using
|force_new_process_for_new_contents| field which this CL removes.


This CL tweaks ExtensionApiTest.WindowsCreateVsBrowsingInstance test
so that:

- The test is closer to what the hangouts extension does
  (it navigates both windows to the same web origin and *then* attempts
  to lookup one window from the other).  Without this modification, the
  test would NOT have caught the hangouts extension regression that was
  almost introduced by https://crrev.com/2873503002).

- The test verifies the opener relationship (i.e. |window.opener|,
  findability via |window.open|, SiteInstance::IsRelatedSiteInstance)
  rather than accidental, indirect manifestations of having an opener
  relationship (i.e. being in the same process or site instance).


Relevant automated tests:
- Tweaked test:
  - ExtensionApiTest.WindowsCreateVsSiteInstance
    (the window.open part passes before and after this CL; the
     window.opener part + the IsRelatedSiteInstance part only pass after
     this CL)
- Other tests:
  - AppBackgroundPageApiTest.Basic
    (hosted app -> background page can violate browsing instance; tests
     handling of mapping of web urls [full url, not just origin] to
     extensions)
  - CtrlClickShouldEndUpInNewProcessTest.* tests
    (tests for behavior that used to depend on the removed
     |force_new_process_for_new_contents| field).

I have also verified that the Hangouts extension (current prod version
- 2017.1019.418.1) works fine before and after this CL (i.e. I have
verified that this CL doesn't regress https://crbug.com/597750).

Bug: 713888
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Test: See above.
Change-Id: If23ac7b72256bfcd695fc4bc3759a5bd73f4812f
Reviewed-on: https://chromium-review.googlesource.com/758801Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516081}

BUG=598073
TBR=yzshen@chromium.org
NOTRY=true

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ibbafcf79f7bf10d1b96f252c94f1b90ec668cf6d
Reviewed-on: https://chromium-review.googlesource.com/767025
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516080}

fix the normalize-ident.html LayoutTest failure.
normalize-ident.html seems like to merge between my patch
which is replaced with Element.attributeSytleMap
pass CQ dry run and merge.

Bug: 784278, 774933
Change-Id: I779b6177399c3e10b6323b6ed891d81e523cfcfe
Reviewed-on: https://chromium-review.googlesource.com/765753Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#516079}

Bug: 783173
Change-Id: I2bcf961155fab34a9a58865ca17ebe28876bab10
Reviewed-on: https://chromium-review.googlesource.com/764118
Commit-Queue: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Zijie He <zijiehe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516078}

This reverts commit d16c535e.

Bug: 
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I978fde2edb396307d896a2027beb04457e5f1972
Reviewed-on: https://chromium-review.googlesource.com/758809Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516077}

Currently when you click on an item in a folder on the
bookmarks bar, the item will flash several times to
provide feedback to the user.

This CL reduces the flashing so that it will only flash
once before closing the menu.

Bug: 640138
Change-Id: I7bbc51ae0f4c4a1aac1d908b41984efb310f3854
Reviewed-on: https://chromium-review.googlesource.com/765094Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Sarah Chan <spqchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516076}

Back then, telemetry_perf_unittest was removed from linux_android_rel_ng because it occasionally get stuck while fetching dependent files from GS.
Two things have changed since then:
1) linux_android_rel_ng is swarmed, which mean we don't run telemetry_perf_unittest in multi-process mode.
2) Dependent telemetry files are prefetched during "gclient sync" (crbug.com/780967)

This CL reenables telemetry_perf_unittest on linux_android_rel_ng to get coverage on Nexus5 devices.

Bug: 725516
Change-Id: Ib5ff018be5d702c3d60ee3a09cf5fdfb36b605d5
Reviewed-on: https://chromium-review.googlesource.com/764570Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#516075}

This CL is a followup to https://chromium-review.googlesource.com/743022.
It adds the missing stride information for single planar frames.

Bug: 555909
Change-Id: Ied15fa15b898dbd17f3dae45788b68a0a286ef24
Reviewed-on: https://chromium-review.googlesource.com/766867Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516074}

This change adds speedometer-future and speedometer2-future benchmarks
to the perf waterfall. These benchmarks enable v8 developers to see the
performance of upcoming VM features that aren't ready to be shipped yet.

BUG=chromium:777818

Change-Id: If77b51046a279706d6f48d6a73733f068a55e91d
Reviewed-on: https://chromium-review.googlesource.com/764403
Commit-Queue: Ashley Enstad <ashleymarie@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#516073}

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Bug: 753436
Change-Id: I10a88bac9831ed86251af6e78185bf5a5d6bdf2b
Reviewed-on: https://chromium-review.googlesource.com/764964Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516072}

Move the ConstantSourceNode tests from the chrome directory to the
the-constantsourcenode-interface directory.

The test failures on Firefox are bugs in Firefox and issues have been
filed.  Safari and Edge fail these because they don't currently
support ConstantSourceNode.

Remove these tests from LayoutTests/webaudio since the WPT tests are
identical except for the script locations (as confirmed by diffing).

Bug: 745778
Change-Id: I2c082834a78437e2d6773ef890dfaf063b3ac49e
Reviewed-on: https://chromium-review.googlesource.com/759023Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516071}

Add code to print out native input for proto fuzzers. Document this and
other miscellanious proto fuzzer things as well.

Bug: 783293
Change-Id: I4b9adbe1f9df2fb16d2b05a33cfe5b12911716b6
Reviewed-on: https://chromium-review.googlesource.com/765567Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Commit-Queue: Jonathan Metzman <metzman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516070}

This patch address an UMA assert failure. It happens because we record
metrics with a null client in most of the tests (the metrics name is
never set). However, some tests that verify UMA buckets do set the name.
In those cases, UMA assert fails since the we are using a different uma
name in the same process.

The fix is to only record UMAs if we have a client name set. Ideally
we would fix this at the test level instead, so I left a TODO.

R=khushalsagar@chromium.org, ericrk@chromium.org

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ida6d605963d123ce683b1c1b8b9814904d17ff45
Reviewed-on: https://chromium-review.googlesource.com/764583Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516069}

Bind Ganesh to //ui/gl provided GL functions. This avoids the need for
linking to system provided EGL and GLESv2 libraries.

Bug: 782871, 782540
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: I04f250ac68b926b25c7563a8fad4f7d939930da2
Reviewed-on: https://chromium-review.googlesource.com/764648Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Reviewed-by: Brian Salomon <bsalomon@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516068}

This change replaces the infobar's custom padding with the
new INSETS_DIALOG padding constant. This causes the infobar's icon
to be aligned with the other controls on the left margin.

Bug: 610428
Change-Id: Idb4c2faaa16004951eaf9988cd768b7dcc359167
Reviewed-on: https://chromium-review.googlesource.com/758558Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516067}

Instead of verifying that a user manually ran the update command, just
run it anyways and block presubmit if there are uncommitted changes
(namely the updated csv and json files).

BUG=chromium:781312

Change-Id: I8f05cd0bf817ca958c608c0e54c87a990ba6848e
Reviewed-on: https://chromium-review.googlesource.com/754062
Commit-Queue: Ashley Enstad <ashleymarie@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#516066}

Bug: 771698, 780542
Change-Id: I751a646cd04ee62eaf9de34df974c6560b82afbe
Reviewed-on: https://chromium-review.googlesource.com/761716Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516065}

Bug: 721395
Change-Id: I0d4c7152dededabbc37d11a0f799837d87930958
Reviewed-on: https://chromium-review.googlesource.com/759696Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516064}

Reading the keyboard device layout property from udev might fail. When
this happens, we used to store the keyboard info with a default layout
value = Layout1.

This CL avoid storing the keyboard info when a failure in udev is detected,
we will still fallback to the default layout for the current key event, but
we will attempt to re-read the layout property from udev on subsequent keys
until a valid layout is returned. This eliminates the need to reboot the
device to exit the bad state.

BUG=783166
TEST=added new test.

Change-Id: I94d6771ef955e20cee831ad0a93e31dcaaf8f610
Reviewed-on: https://chromium-review.googlesource.com/764444Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516063}

mocha.grep() does substring matching, which causes accidentally running
some tests multiple times. Strengthen the RegExp passed to mocha.grep()
to ensure that no sub-string matching occurs.

This CL deploys the new runMochaTest() method in MD Extensions only.
Remaining WebUI tests will be updated in follow up CLs.

Before this CL there were actually a couple of tests accidentally run
multiple times, fixed now.

Bug: 783334
Change-Id: I63fe4fc327f5a2bba4307b087380f1883d337cc1
Reviewed-on: https://chromium-review.googlesource.com/761981
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516062}

Add a custom GLSurfaceOSMesaPng that outputs to file. Unfortunately the
GPU sandbox will block this from writing to file, so it only works
without the GPU sandbox.

Bug: 783792
Change-Id: I868702aa5dab81bffb8ea4867d659225255e5d50
Reviewed-on: https://chromium-review.googlesource.com/758608
Commit-Queue: kylechar <kylechar@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516061}

The behavior is tested by NetworkContextConfigurationBrowserTest.Cache,
and the latter uses the correct URLRequestContext when the network
service is in use.

In another CL, I'll be switching the vestigal in-process system
URLRequestContext to use default parameters when the network service is
enabled, which will cause that context to use an in-memory cache. When
the network service is disabled, the legacy URLRequestContext will
still have no cache.  Seems best to just remove the test, since it's
redundant.

Bug: 754007
Change-Id: I0ce14ee613cf0d400d6fc86e8931eae370df13f5
Reviewed-on: https://chromium-review.googlesource.com/766951Reviewed-by: Randy Smith <rdsmith@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516060}

Convert the remaining settings sections that are similar to copies and
layout.

Bug: 773928
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I987905956434e37ac5a5409454c87a1f6babb900
Reviewed-on: https://chromium-review.googlesource.com/759679Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516059}