GitLab

This CL makes webapps always navigate as a result of
clients#openWindow()
In particular:
- The CL moves WebApkConstants#EXTRA_WEBAPK_FORCE_NAVIGATION to
ShortcutHelper
- Sets the extra in ServiceTabLauncher#launchTab() for webapps

BUG=744843
NOPRESUBMIT=true
(Because the version in shell_apk_version.gni does not need to
be incremented because although I renamed
WebApkConstants#EXTRA_WEBAPK_FORCE_NAVIGATION I did not change
its value)

Change-Id: I98465c1f8773a705dc7177792256d901bf9aa6bc
Reviewed-on: https://chromium-review.googlesource.com/575328
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488831}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/9629af753335..b5d2ffa3c55a

$ git log 9629af753..b5d2ffa3c --date=short --no-merges --format='%ad %ae %s'
2017-07-21 xunjieli [wpr-go] When the entire url string matches, calculate a match ratio of request headers
2017-07-21 loloangela Fix errors related to bad-continuation
2017-07-21 loloangela Fixed errors related to bad-continuation
2017-07-21 loloangela Fixed errors related to bad-continuation

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: I008fe48cd29767266ca0e60bf940f91185ed057c
Reviewed-on: https://chromium-review.googlesource.com/582152
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488830}

This implements logic to evict from SW image decode cache
in cc, based on skia unique image id. We add a auxiliary
map of image id and key, and use it for optimizing search
and access. New api's to handle cache addition and deletion
is also added.

BUG=734982
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

patch from issue 2951093002 at patchset 80001 (http://crrev.com/2951093002#ps80001)

Change-Id: Iab533d140802a0308bf2143765708257a465bd31
Reviewed-on: https://chromium-review.googlesource.com/571459Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Reviewed-by: Sohan Jyoti Ghosh <sohan.jyoti@huawei.com>
Commit-Queue: Sohan Jyoti Ghosh <sohan.jyoti@huawei.com>
Cr-Commit-Position: refs/heads/master@{#488829}

 - Remove obsolete check and tests from js_checker.py
 - Convert Downloads page to use let/const as a proof of concept that it works.

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

This returns the resource id in case the HUD canvas
is invalid, because of context loss while SkSurface
creation. The resource is subsequently evicted from
quad list.

BUG=736127
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

patch from issue 2961633002 at patchset 160001 (http://crrev.com/2961633002#ps160001)

Change-Id: I8d04dfed24ec9cd7e2b520d20988b7a70efcacc3
Reviewed-on: https://chromium-review.googlesource.com/571821Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Reviewed-by: Sohan Jyoti Ghosh <sohan.jyoti@huawei.com>
Commit-Queue: Sohan Jyoti Ghosh <sohan.jyoti@huawei.com>
Cr-Commit-Position: refs/heads/master@{#488827}

UserEvents are created and reference sessions data by global_id. It is
important that they travel over the wire in this format, as this is how
the sessions data is keyed into Footprints, and the sync server cannot
feasibly perform a persistent read before writing new UserEvents.
Because global_id is forced to be part of the wire interface and
specifics, it is also conveniently part of the interface to the
UserEventService.

However, while this global_id is seemingly sacred to sync, it comes
from simply the timestmap of the navigation entry. And if a page is
reloaded, this value can change. A problem arises when a UserEvent
references a navigation by a global_id that was updated and the old
value is never going to reach the sync server.

To fix we maintain two sets of mappings, one that allows us to map old
global_ids to new global_id, and one that allows us to efficiently look
up uncommitted UserEvents by global_id, so that if we get either a new
global_id or a new UserEvent we can quickly fix the global_id.

BUG=747621

Review-Url: https://codereview.chromium.org/2958303002
Cr-Commit-Position: refs/heads/master@{#488826}

Follow-up from https://codereview.chromium.org/2975523002/

Bug: 667560
Change-Id: Ic562500db2fc352f7938306ba3408e18e57a55dc
Reviewed-on: https://chromium-review.googlesource.com/575444
Commit-Queue: Will Chen <chenwilliam@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488825}

Compile-time constants returned by methods that are not constexpr,
not even static?  Wait, there's a better solution!  (These methods
are leftover from SPDY days when frame sizes were different for
different SPDY versions.)

This CL lands server change 162294268 by bnc.

BUG=488484

Change-Id: Idf6feb66ca5aac69faccb2ce9fe05c53327b819c
Reviewed-on: https://chromium-review.googlesource.com/581432
Commit-Queue: Dianna Hu <diannahu@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Reviewed-by: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488824}

Revert "viz: Make hit testing mojoms match README.md"

This reverts commit af391815.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> viz: Make hit testing mojoms match README.md
> 
> This CL moves hit_test code to match the directory structure in README.md.
> 
> Bug: 722935
> Change-Id: I1565e9de3ec9387e13651b4a89d623bbc4267773
> Reviewed-on: https://chromium-review.googlesource.com/581798
> Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
> Commit-Queue: Fady Samuel <fsamuel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#488820}

TBR=rjkroege@chromium.org,fsamuel@chromium.org,tsepez@chromium.org

Change-Id: Id074cbea1cde58042e55cbc8ce24ac7c178afc10
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 722935
Reviewed-on: https://chromium-review.googlesource.com/582528Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488823}

This reverts commit c1405389.

Reason for revert: trying a different approach.

Original change's description:
> [vr] Restore opacity when transient elements are shown again.
> 
> We'd previously set opacity to 0.0 when hiding elements in the
> transience manager which makes it tricky to see them when they come
> back. With this change, we inform the manager of the desired "opacity
> when visible" and it will restore elements to that opacity when
> shown again.
> 
> Bug: None
> Change-Id: I1a941c3032c35adab5afed17a8afc60bd41230f5
> Reviewed-on: https://chromium-review.googlesource.com/582069
> Commit-Queue: Ian Vollick <vollick@chromium.org>
> Reviewed-by: Christopher Grant <cjgrant@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#488788}

TBR=vollick@chromium.org,cjgrant@chromium.org,ymalik@chromium.org

Change-Id: Ic3ec7b20a980b42c1048c0d074cff6136c3997c2
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/582527Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488822}

Summary of changes needed for the migration:
 - Excluded URLs behavior is different than Vulcanize, need to explicitly list
   all URLs to be excluded (unlike Vulcanize, transitive deps of an excluded
   URL are not implicitly excluded).
 - Excluded URLs need to match exactly, unlike Vulcanize where foo.html would
   match chrome://some-path/foo.html.
 - Input HTML files need to have
   <html><head>...</head><body>...</body></html> tags.
 - A single invocation of poylmer-bundler produces both "basic" and
   "lazy" modules (achieved by using the --shell flag), unlike Vulcanize
   which required two separate invocations.
 - Using new --manifest-out instead of previous --out-request-list flag to
   generate depfiles for Ninja.
 - Using --rewrite-urls-in-templates to preserve previous rewriting behavior.
 - polymer-bundler does not blow up when it can't find a file (unlike Vulcanize,
   so check output manifest for any reported "missing" dependencies).
 - Removed some Windows specific hacks that don't seem necessary anymore.

BUG=731881
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2936333002
Cr-Commit-Position: refs/heads/master@{#488821}

This CL moves hit_test code to match the directory structure in README.md.

Bug: 722935
Change-Id: I1565e9de3ec9387e13651b4a89d623bbc4267773
Reviewed-on: https://chromium-review.googlesource.com/581798Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488820}

Replaces GURL, CORSMode and UrlIndex parameters with UrlData.

Change-Id: I42e723381ad53c3a9d33289b3da585d5d825f587
Reviewed-on: https://chromium-review.googlesource.com/581610Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Commit-Queue: Alok Priyadarshi <alokp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488819}

Previously, the importer would check for exportable Chromium commits and
abort if any existed. This CL would make it so that instead of aborting,
the importer would apply the patch to the local WPT before copying
files over.

This should make it so importer is no longer blocked on exporter in
general, but it should still be the case that exportable Chromium changes
aren't clobbered.

Bug: 734121
Change-Id: I5ca08df2f38a3afe2c98af1cfa8ef1f1ac44eceb
Reviewed-on: https://chromium-review.googlesource.com/580574
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Jeff Carpenter <jeffcarp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488818}

Previously, when a scan began, we would clear all existing scan results
from the cache, then add results back to the cache as the scan
progressed. This was janky because it would result in the UI removing
Tether networks and then adding them back shortly afterwards when scan
results came in.

This CL changes this functionality so that results are only removed
after a scan ends and the associated device is not found.

Bug: 672263, 746726
Change-Id: I6df2516b1bc0e604c3a496838804bc6ee5c8292c
Reviewed-on: https://chromium-review.googlesource.com/581633
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488817}

This modifies the trial in http://crrev.com/2a248c5

Bug: 734132
Change-Id: I6f0453465451023d33c8505f8b9f997004d5a094
Reviewed-on: https://chromium-review.googlesource.com/566335
Commit-Queue: Catherine Chung <catherinechung@google.com>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488816}

This change:
  - Does a separate pass on all histograms, validating them, before
    starting to prepare their deltas. This will confirm that data is
    bad already before we start processing them (i.e. verify that it's
    not the processing code having some side effect).
  - Counts the number of corrupted histograms to tell us if it's a single
    bad value or more widespread corruption.
  - Keeps track of the last histogram that someone logged something to,
    so that we could have a trail of the last thing that happened before
    corruption.
  - Moves a previously added instrumentation call to within the correct if
    block.

BUG=736675,744734

Change-Id: I4b860ad6e977c1555409bd628f9e4e5147e61654
Reviewed-on: https://chromium-review.googlesource.com/581418
Commit-Queue: Alexei Svitkine (slow) <asvitkine@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488815}

This CL changes label imageset to image-set (or ImageSet), because afaik
image-set is a html/css concept and imageset is not.

TBR=tommycli@chromium.org

Bug: None
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Iac23276f11b27f8863b3f7aaf864c8986f647fd9
Reviewed-on: https://chromium-review.googlesource.com/582194
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488814}

Mid-word-break algorithm kicks in when CSS properties such as
'word-wrap: break-word' is used. Logically speaking, we should layout
as normal, and break words if overflow occurs.

However, Blink has 2em heuristic limit because of the performance
problem in certain cases. This means Blink measures characters that go
beyond the right edge only up to 2em before it starts mid-word-break.
See the previous CL[1] for more details.

This patch adjusts it to 4em. The longest common ligature is Emoji ZWJ
sequence, and its v5.0[2] can ligate 4 Emoji into 1 at maximum. To
handle this, 3em overflow is needed, and 1em for a rainy day fund.

[1] r403830, https://codereview.chromium.org/2077313002
[2] http://unicode.org/emoji/charts/emoji-zwj-sequences.html

Bug: 746222
Change-Id: Ic58b58716502f4ae9a06c1e91d2f5de944bc7978
Reviewed-on: https://chromium-review.googlesource.com/581249Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488813}

This patch plumbs PaintImage into PaintShaders instead of SkImage.
With the patch to not construct SkPaint and instead using PaintFlags,
it becomes possible to introspect the flags to pull off PaintImage used
to construct it.

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

Change-Id: Ia01ce40b1586b90172421ba99009baeb604fd937
Reviewed-on: https://chromium-review.googlesource.com/576868Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488812}

R=robliao@chromium.org

Bug: 689520
Change-Id: Id5e138389b16c02a612d000007c2447cd1e2701d
Reviewed-on: https://chromium-review.googlesource.com/580527Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488811}

The w3c spec indicates that parsing an unsupported value for referrer
meta tags should not result in a referrer policy change.  However, when
WKWebView detects one of these tags, it will change the policy to
'never'.

testWebReferrerOpenInNewTab verifies this observed behavior of WKWebView
but https://codereview.chromium.org/2918313002/ updated
ReferrerPolicyFromString() to assume strict adherance to the latest spec
rather than WKWebView's actual implementation.  This change updates the
context menu param construction to use 'never' for unsupported referrer
meta tag values so that the policy is consistently defaulted to 'never'
for pages that are opened in a new Tab.

w3c spec: https://w3c.github.io/webappsec-referrer-policy/#unknown-policy-values

Bug: 733202
Change-Id: I74772f799a78c726601debddf64dd8f9ebbb2e0e
Reviewed-on: https://chromium-review.googlesource.com/580630
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488810}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/913ccf82..d725114e

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

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=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org

Change-Id: I7c1bf2d1fb39c5970fa70538e96ad5e36ba533f4
Reviewed-on: https://chromium-review.googlesource.com/582078Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488809}

SwiftShader's linear texture filtering precision was insufficient to
pass some of the layout tests. In order to have the option to switch
between high precision and high performance, a new chromium extension
was added and implemented in SwiftShader. That extension is now added
in this cl, along with the appropriate usage which would trigger high
precision filtering within SwiftShader when running layout tests.

Bug: 726075
Change-Id: I69406e460595225b2436bb393f64144ff3ad7a1a
Reviewed-on: https://chromium-review.googlesource.com/579787Reviewed-by: Geoff Lang <geofflang@chromium.org>
Reviewed-by: John Bauman <jbauman@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488808}

The typemapping makes it super error-prone and painful to add fields and
now that we are out of base/ we don't need it anymore!

Bug: 728199
Change-Id: I1312aad0811291ec6cf69aa83d79fbb6d1a6aa84
Reviewed-on: https://chromium-review.googlesource.com/567185Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488807}

This eliminates the inconsistent 'beaker' image and replaces it with
a new image. It also merges the 'loading' image with the default image.

Bug: 709917
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I139d8555c2beb7417d1e79b128ae5ca680258084
Reviewed-on: https://chromium-review.googlesource.com/578556Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488806}

V8 change was rolled to Chromium.

TBR=dgozman@chromium.org

Bug: 744797
Change-Id: I5a22edb0c1cc76a4f13bf6b9a9ac576e3df38065
Reviewed-on: https://chromium-review.googlesource.com/582082Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488805}

This reverts commit 317adc6a.

Reason for revert: Caused MSAN test failures.

https://luci-milo.appspot.com/buildbot/chromium.memory/Linux%20ChromiumOS%20MSan%20Tests/1887

Original change's description:
> Implement metalayer palette tool in ash.
> 
> Add a new "highlighter" tool using the same fast
> rendering method as laser pointer (CL extracting
> the common base class is to follow).
> 
> Bug: b:63142451
> Change-Id: Id848b77f08ae95c167c527a07aec6ccdf79f49f4
> Reviewed-on: https://chromium-review.googlesource.com/558467
> Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
> Reviewed-by: David Reveman <reveman@chromium.org>
> Reviewed-by: Jacob Dufault <jdufault@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#488688}

TBR=kaznacheev@chromium.org,reveman@chromium.org,oshima@chromium.org,lhchavez@chromium.org,jdufault@chromium.org

Change-Id: Ifaf586a4374e2bde5abd8d4adecb95bd108f9dea
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: b:63142451
Reviewed-on: https://chromium-review.googlesource.com/582428Reviewed-by: Ojan Vafai <ojan@chromium.org>
Commit-Queue: Ojan Vafai <ojan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488804}

Fixed the nit from:
https://chromium-review.googlesource.com/c/577114

Bug: None
Test: Compiles
Change-Id: Ic04e6748532ec6db57b9f7d73121c7b25105c6ed
Reviewed-on: https://chromium-review.googlesource.com/582199Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ryan Chung <ryanchung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488803}

Bug: 747052
Change-Id: I4312c56fc27209167437ba8188d1e2cbd5930565
Reviewed-on: https://chromium-review.googlesource.com/580359
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488802}

Add i2s loopback in order to enable the reference channel for AEC.

Bug: http://b/38428792
Test: built cast_shell_internal_apk, ran assistant with AEC
Change-Id: Ie8c1ecf09bc31050e3cfe61eddf69dc21aba1fce
Reviewed-on: https://chromium-review.googlesource.com/566063
Commit-Queue: Nat Jeffries <njeff@google.com>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488801}

HostResolverImpl used to pass all non-numeric host names it received,
including invalid ones, to the system HostResolver. That was changed
in https://chromium-review.googlesource.com/569298 (Since the bad
addresses could be sent over the wire with the async resolver, and
it generally seemed like a bad idea).  And all was right with the world.

Then a DCHECK was added to SystemHostResolverCall for invalid hostnames,
since it should no longer be called with them in production. However,
it turns out the MockHostResolver calls that method directly, bypassing
HostResolverImpl, and does so with IPv6 host names (Or whatever other
stuff is passed to it). In particular, the socks_client_socket_fuzzer
does this by passing in "::1".  This is a legal use of the
MockHostResolver API, not a bug in the fuzzer.  So this CL modifies
MockHostResolver not to do that.

Bug: 747243
Change-Id: Ib4be76f1d03f33bc65a493ac73aae6407ca3383d
Reviewed-on: https://chromium-review.googlesource.com/581788
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488800}

Use a box of six panels in lieu of a GL background color. The floor and
ceiling are now additional elements, drawn later, because they are
selecxtively enabled and disabled based on mode.

Other assorted cleanup along the way.

BUG=

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

Bug: 725977
Change-Id: Ia44202d2c6f316fa76c32dc3d1f56f0a4b15dc68
Reviewed-on: https://chromium-review.googlesource.com/575583
Commit-Queue: min c <minch@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Terry Anderson <tdanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488798}

TODO(robertshield): remove this call and everything that falls off of it.

R=robertshield@chromium.org, thakis@chromium.org

Bug: 667892, 747557
Change-Id: I1ddad1db01f18db6b7121945c1313933c9e2e16b
Reviewed-on: https://chromium-review.googlesource.com/581634
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488797}

This CL rolls EarlGrey to f456370981a612d73eb79df7acf3e7303755e160 to
pick up the latest changes and prepare for iOS 11.

BUG= 747116

Change-Id: Idf15fe28e124e99f99740fdee0b79e9de969e406
Reviewed-on: https://chromium-review.googlesource.com/581930
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Mike Baxley <baxley@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488796}

This surface ID should still be contained in referenced_surfaces_, but
there are crashes sometimes because the iterator from find is invalid.
Add CHECKs to see if we're attempting to remove the wrong surface id,
or if it's just not found in the structure.

Bug: 745684
Change-Id: Idf4a94f01e55ec20c51b6f72a4c7603c40226df6
Reviewed-on: https://chromium-review.googlesource.com/580404
Commit-Queue: John Bauman <jbauman@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488795}

Bug: 747138
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I77e1b33f74f91e5918d9a74f9a79cd8b0de79fc6
Reviewed-on: https://chromium-review.googlesource.com/580675Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488794}

The destruction callback of a GpuMemoryBufferImpls can be called on any
thread[1]. So make sure the destruction callbacks hops onto the correct
thread before mutating local data structures or sending mojo messages.

[1] See doc for GpuMemoryBufferImpl::CreateFromHandle()
https://cs.chromium.org/chromium/src/gpu/ipc/client/gpu_memory_buffer_impl.h?l=28

BUG=733482

Change-Id: Ifc3fecd6a8bb42aa61f3d2d9667bd0e931d7261c
Reviewed-on: https://chromium-review.googlesource.com/565858
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488793}

Previously it would not search any of the native language names, resulting
in missing results.

Bug: 746880
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I6fb39d532eb87bf138c22018ca81638b1083a969
Reviewed-on: https://chromium-review.googlesource.com/580250
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488792}