GitLab

I don't work on Chrome any more and don't check my @chromium.org email
too often. I don't want to slow folks down that mistakenly choose me as
a reviewer.

R=dpapad@chromium.org
BUG=none

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I847c43ef2b6dab51bf22e3685022532d49ac1a98
Reviewed-on: https://chromium-review.googlesource.com/582204
Commit-Queue: Dan Beam (no longer on Chrome) <dbeam@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rachel Blum <groby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488842}

Replaces non-serialization uses of To/FromInternalValue() with
reasonable alternatives. No behavior changes intended.

Also includes a few minor clean-ups, such as deleting the
cc::TimeUtil::Scale() and Mod() methods in favor of built-in
operator overloads.

Testing: Ran cc_unittests and a local chrome browser build to
confirm correctness.

Bug: 634507
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1e9360d707aacad3a88474058f0d0c96d57f0d80
Reviewed-on: https://chromium-review.googlesource.com/578691
Commit-Queue: Yuri Wiitala <miu@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488841}

This CL adds elasticity to the simple gesture nav UI. After it reaches
the activation threshold, the affordance would be in its final shape
(full opacity, centered arrow, full ripple size), however it would still
move with further drags with diminishing speed until it completely
stops. Further drags would be ignored.

BUG=668296
TEST=manual

Change-Id: I7423e441bf90c04b84fda2cf9ddde44745bc945e
Reviewed-on: https://chromium-review.googlesource.com/559592
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488840}

This is also failing on Win7 Debug along with the other video tests.
They both seem flaky, so likely have the same root cause.

BUG=746128
TBR=johnme@chromium.org

Change-Id: I3622dc76166bc229222f4966eb2bafcfac7de0f1
Reviewed-on: https://chromium-review.googlesource.com/582470Reviewed-by: Ojan Vafai <ojan@chromium.org>
Commit-Queue: Ojan Vafai <ojan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488839}

Bug: 740070
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I3b4b73df9598d474af0e6f36494b06c54bbdde2a
Reviewed-on: https://chromium-review.googlesource.com/578658
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Walter Korman <wkorman@chromium.org>
Reviewed-by: Alexandre Elias <aelias@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488838}

Before mojofication on Hid, we have to add typemapping for HidDeviceId first.
HidDeviceId is defined as uint64_t on MacOS while as string on other
platforms.

In this CL, we rename the original HidDeviceId to HidPlatformDeviceId, and
define the new HidDeviceId type as uint64_t. we map the PlatformHidDeviceId
to HidDeviceId. 

All clients of HidService should hold the new HidDeviceId instead of the
PlatformHidDeviceId.

BUG=728223

Change-Id: I3585c9eb0eacb02571258314c14e063adce653fc
Reviewed-on: https://chromium-review.googlesource.com/570201Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Ke He <ke.he@intel.com>
Cr-Commit-Position: refs/heads/master@{#488837}

GetBlockingPool() is replaced by SequencedTaskRunner. There's no
per-task trait in SequencedTaskRunner, so the shutdown behavior are
all set to BLOCK_SHUTDOWN.

Bug: 667892
Change-Id: I6e8f2507b201a8cb077d7338f504684ca1e232c8
Reviewed-on: https://chromium-review.googlesource.com/580620Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488836}

Includes changes to:
- Include the bootstrap service and default configuration in the bootfs.
- Support mmap()ing of files on tmpfs filesystems.

Bug: 707030
Change-Id: I4d3df8a0c2acc7bfaaa957f298dfddc8f567cbcb
Reviewed-on: https://chromium-review.googlesource.com/582048
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488835}

https://pdfium.googlesource.com/pdfium.git/+log/d0856ba49c2b..06ac9c95c252

$ git log d0856ba49..06ac9c95c --date=short --no-merges --format='%ad %ae %s'
2017-07-21 thestig Clarify --build-dir help info in safetynet_measure.py.

Created with:
  roll-dep src/third_party/pdfium


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


TBR=dsinclair@chromium.org

Change-Id: I748d7ea6a5c6c749d5c09474335fa613033b935b
Reviewed-on: https://chromium-review.googlesource.com/582335
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488834}

This is a reland of c1405389
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=cjgrant@chromium.org

Bug: 747633
Change-Id: I340ed94f61f016243dc4495d687cab1d58ea2e67
Reviewed-on: https://chromium-review.googlesource.com/582529Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488833}

which trips on DCHECKs. Instead of DCHECK'ing, recalculate the values.

Bug: 463729
Change-Id: I073348377f17faa86768cf871dd5c900167e9e3c
Reviewed-on: https://chromium-review.googlesource.com/580614Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Michael Nordman <michaeln@chromium.org>
Cr-Commit-Position: refs/heads/master@{#488832}

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}