GitLab

http://crrev.com/493874 changed the low delay case to wait for two
frames since we need to be sure we don't resume until we actually
have valid frames since the first frame was valid forever without
duration information.

It turns out we actually do have duration infromation hanging off
the DecoderStream, so use this information and set it as the
FRAME_DURATION metadata key for each VideoFrame.

We can then have the algorithm use this information for the
estimated end time of frames when only a single frame is present
in the queue.

Note: The video-canvas layout test was showing the wrong frame;
I manually extracted the frames and verified that before we were
showing the "7" frame when pts=2.0s == "6" frame. I've updated
the test expectations appropriately.

BUG=786576,767878,709302
TEST=new unittest, old unittests pass w/o modification, manual
test of 4k60 vp9 low latency content doesn't exhibit multiple
stalls after returning to the foreground when the video track
has been disabled, manual test with https://jsfiddle.net/u3enjLzz/

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: I963903d6a173038a2d534db4e040c8f4774825b5
Reviewed-on: https://chromium-review.googlesource.com/780267
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519961}

Modify url type from DOMString to USVString to match the specification.
https://html.spec.whatwg.org/multipage/dom.html#documents

Bug: 
Change-Id: I61cf2d2eee439675607504bdc048844e236b7310
Reviewed-on: https://chromium-review.googlesource.com/790117Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Bhagirathi Satpathy <bhagirathi.s@samsung.com>
Cr-Commit-Position: refs/heads/master@{#519960}

* Follow up to comments from https://crrev.com/c/767663
* Also limit archived_binaries from DMGs
* Add metrics so we can see how many we're dropping.

Bug: 774664
Change-Id: I2f901ad612763f36f84e8ea2cbb1b8d8909d9509
Reviewed-on: https://chromium-review.googlesource.com/773789Reviewed-by: Luke Z <lpz@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Nathan Parker <nparker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519959}

This was public because GpuImageDecodeCache used skia to get the decode,
which is not required anymore. Going forward we should eliminate this
within PaintImage itself.

R=vmpstr@chromium.org

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Id34affc108d4f13f6aae53c19da61a884823b5b9
Reviewed-on: https://chromium-review.googlesource.com/779768Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519958}

We throw errors when certain extensions (unpacked with an event page)
try to use the deprecated sendRequest-related properties of the
chrome.extension API. Implement this for native bindings. In order to
do this, add an InitializeInstance() method on native binding hooks
that allows hooks to modify the newly-created instance of an API for a
specific context.

Add unittests for both InitializeInstance and the restriction of
sendRequest properties.

Bug: 653596

Change-Id: I22be1f0f9d4f299e127b21084649000bab63ddfa
Reviewed-on: https://chromium-review.googlesource.com/775516
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519957}

The spec defines what it means for a type to 'match' something. This
patch implements this concept and tests it on CSSPositionValue, which
only accept CSSNumericValues that 'match' a <length-percentage>.

https://drafts.css-houdini.org/css-typed-om-1/#cssnumericvalue-match

Bug: 776173
Change-Id: I4f893fa879da1221b37851a593c20d018794d566
Reviewed-on: https://chromium-review.googlesource.com/788482
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: Renée Wright <rjwright@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519956}

Bug: 785178,771438
Change-Id: I8921095df30541830d45b959892adcc182598e5b
Reviewed-on: https://chromium-review.googlesource.com/795350Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519955}

Support Arc vpn provider UI support in Chrome://settings page

Bug: 784573
Test: Manual
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I1fde7f3ed3dce9243f444578f7e24e0e44ac1c66
Reviewed-on: https://chromium-review.googlesource.com/757760
Commit-Queue: Long Cheng <lgcheng@google.com>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519954}

The Geolocation struct used to hold a string-type error property,
but was changed into a boolean here:
https://codereview.chromium.org/1917543002

There was a mistake in that CL, where it was still expecting a
string-type error, causing serialization to always return an
empty string.

This CL fixes the serializer, allowing the last applied
geolocation to be saved.

Bug: 649657
Change-Id: I7f65f7844dca9ee2e182970602c6810a3c776973
Reviewed-on: https://chromium-review.googlesource.com/778044
Commit-Queue: Erik Luo <luoe@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519953}

The result of this CL should be that the frames submitted by the
VideoFrameSubmitter now have complete information and thus should show
up on the screen.

This CL accomplishes this mainly through a refactor of VideoLayerImpl
shared functions into VideoResourceUpdater, making them accessible to
VideoFrameSubmitter.

Bug: 746182
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I6cfe9d181e3cde4c13299c42df40ab73480a0587
Reviewed-on: https://chromium-review.googlesource.com/701917Reviewed-by: enne <enne@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519952}

https://chromium.googlesource.com/angle/angle.git/+log/5201ce127afe..57ea533f79a7

$ git log 5201ce127..57ea533f7 --date=short --no-merges --format='%ad %ae %s'
2017-11-22 kainino TType: Store array sizes vector as a pointer.

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


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
TBR=jmadill@chromium.org

Change-Id: I8a07cc8a90652fa867b2b0d094dd7681f08fc122
Reviewed-on: https://chromium-review.googlesource.com/795091Reviewed-by: angle-deps-roller . <angle-deps-roller@chromium.org>
Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519951}

Previously, try-flag reported all unexpected passes, even if the failure
expectation came from the main TestExpectations file.  This produced a lot of
irrelevant noise.

Now, try-flag only reports unexpected passes of tests that have flag-specific
failure expectations.

The --flag argument is no longer optional.

Bug: 755401
Change-Id: Ifa507e19159b8cdadf63752f5c8aa2635de014d5
Reviewed-on: https://chromium-review.googlesource.com/794877
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519950}

Building Chrome with /permissive- (a fussy variant in the VC++ compiler)
reports warnings in openvr because exception specifications were removed
from jsoncpp.cpp but not from json.h. The error is:

    jsoncpp.cpp(2599): warning C5043: 'Json::Exception::what':
    exception specification does not match previous declaration

Removing the throw() specifications from json.h restores consistency and
is what was originally intended.

Change-Id: I6146b6299e23f11b35bc1aefd9640541bbbbe953
Reviewed-on: https://chromium-review.googlesource.com/794830Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519949}

See the bugs and cxx post for justification and details:
https://groups.google.com/a/chromium.org/forum/#!topic/cxx/RkOHzIK6Tq8

This change was done using clang-tidy as described here:
https://chromium.googlesource.com/chromium/src/+/lkcr/docs/clang_tidy.md

In some cases the the tool leaves behind a string of commas where it
replaced a member initializer list
(https://bugs.llvm.org/show_bug.cgi?id=35051). They were cleaned up with:
  git diff --name-only | \
    xargs sed -E -i 's/(^\s*|\)\s*):[ ,]*= default/\1 = default/'

BUG=778959,778957

Change-Id: Ifb34f30c497b206cca6b0656f60b0655409771ba
Reviewed-on: https://chromium-review.googlesource.com/790030Reviewed-by: Mike Klein <mtklein@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Chris Watkins <watk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519948}

See the bugs and cxx post for justification and details:
https://groups.google.com/a/chromium.org/forum/#!topic/cxx/RkOHzIK6Tq8

This change was done using clang-tidy as described here:
https://chromium.googlesource.com/chromium/src/+/lkcr/docs/clang_tidy.md

In some cases the the tool leaves behind a string of commas where it
replaced a member initializer list
(https://bugs.llvm.org/show_bug.cgi?id=35051). They were cleaned up with:
  git diff --name-only | \
    xargs sed -E -i 's/(^\s*|\)\s*):[ ,]*= default/\1 = default/'

BUG=778959,778957

Change-Id: I711cc802211d1bd42dc720eb385e5bf60e95d115
Reviewed-on: https://chromium-review.googlesource.com/788645Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Chris Watkins <watk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519947}

Introduce a JSRunner class to handle safely running JS functions in the
renderer. We abstract this out for testing purposes, since in a real
build we have to worry about things like JS being suspended, while in a
testing in environment we don't. Prior to this, we curried around
callbacks throughout the binding system. This led to nearly every object
taking a "run_js" member, and makes expanding (e.g. to have a
run_js_sync version) painful.

Instead, create a common JSRunner class that can handle running JS
functions in different manners. This class is a per-thread singleton,
and can be overridden for testing.

The test versions also allow us to have more granularity around when we
allow/expect errors in JS execution, vs before where we had to either
allow all errors or none.

Bug: 653596
Change-Id: Ic5d16faaf3757cae60033850580f13689fa5b9a1
Reviewed-on: https://chromium-review.googlesource.com/776650
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519946}

BUG=chromium:684679

Change-Id: If9a0ef6666b41e4f214a6334bfc6e4c3f5d84a3d
Reviewed-on: https://chromium-review.googlesource.com/793811
Commit-Queue: Roman Sorokin <rsorokin@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519945}

This is a preliminary change for implementing charset replacement in
XHR on top of ParsedContentType.

This CL
 - Adds iterator getters for ParsedContentHeaderFieldParameters.
 - Makes ParsedContentHeaderFieldParameters a list of parameters
   instead of a dictionary.
 - Holds unmodified header names instead of lowered names.
 - Removes is_valid_ from ParsedContentHeaderFieldParameters, and adds
   the boolean (as part of Optional) to its holders.
 - Removed Mode::kStrict which can be checked after the parameters are
   parsed.

Bug: 651750
Change-Id: I35db41bee74de8ef33b0b95ae56d039599c5b556
Reviewed-on: https://chromium-review.googlesource.com/781208Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519944}

We know that current context is set to null when the crash happens.
Getting the stack trace for the last call to SetCurrent will be helpful.

BUG=724999

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: Ie99e7c6cd0c9faa162cd0fc789c23d321256ded7
Reviewed-on: https://chromium-review.googlesource.com/780391Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519943}

r516772 was the last of many commits that resolved a number of problems
that made this test suite flaky on Windows. This CL enables tests that
had been disabled over time due to flakes, yet now seem to run okay.

BUG=504054,764415
This CL was uploaded by git cl split.

R=lazyboy@chromium.org

Change-Id: Ibcd290d03dbfb923077ee542c24b06fdb9f21e2b
Reviewed-on: https://chromium-review.googlesource.com/784851Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519942}

https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+log/9cb03e5705c1..18c815f81428

$ git log 9cb03e570..18c815f81 --date=short --no-merges --format='%ad %ae %s'
2017-11-28 dalecurtis Update chromium patches README with new patches.
2017-11-28 dalecurtis Free opus extradata before reallocating.
2017-11-28 dalecurtis Don't manipulate duration when it's AV_NOPTS_VALUE.
2017-11-28 dalecurtis Respect AVERROR codes returned by ogg parsers.
2017-11-25 michael avformat/aacdec: Fix leak in adts_aac_read_packet()

Inspection of code reveals that we don't properly ignore invalid codec
parameters when setting up the ffmpeg demuxer, so we will now explicitly
discard streams which don't have a codec detected.

Created with:
  roll-dep src/third_party/ffmpeg

BUG=788550,787803,773637,787351
TEST=ubsan/asan no longer fail.

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: I87b0482499e41b2c0190ef3852ed81c3e91c4236
Reviewed-on: https://chromium-review.googlesource.com/794844
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519941}

It was modifying a style sheet from another origin to hide some UI
elements when capturing was stopped. This CL makes it add another sheet
instead.

Bug: 788061
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I734543786e80d5046b93fda1e970f9e5e40f6096
Reviewed-on: https://chromium-review.googlesource.com/794542Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519940}

The template message implies that the callback must be run before destroyed.
This has caused confusion for me, and others, e.g. see
https://bugs.chromium.org/p/chromium/issues/detail?id=788658#c4. Instead, the
error should state that either: the callback should be run before it is
destroyed, or else it should be destroyed after the pipe is closed.

Bug: 
Change-Id: Iad5a75332fe2284538ef1d428a6e4572fdc2b551
Reviewed-on: https://chromium-review.googlesource.com/794571Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519939}

ExtensionService has no subclasses, so there's no reason to mark any of
its methods as virtual. De-virtualize a few that were.

Bug: None

Change-Id: Ia23c59ee6d592150ebb802574837bc047af2d50e
Reviewed-on: https://chromium-review.googlesource.com/794052Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519938}

Move AssociatedInterface{Provider,Registry} into blink/common so blink
can use them. Add an accessor in LocalFrame to provide access to the
RenderFrame's AssociatedInterfaceProvider.

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I412f3b559a9777609b2998206970f5c16d43f0c4
Tbr: jam@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/706740
Commit-Queue: Sam McNally <sammc@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519937}

Add internet_page_browser_proxy to hold Chrome.send() for external VPN
providers which are not going to be depericated.

Bug: 784573
Test: Manual
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Icfcab81de857864611c4a0cde89245853513bcc5
Reviewed-on: https://chromium-review.googlesource.com/779712
Commit-Queue: Long Cheng <lgcheng@google.com>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519936}

* last_user_activity_time
* last_activity_day
* last_mouse_time
* last_key_time
* recent_time_active_sec
* device_mode
* device_type
* battery_percent
* on_battery

Bug: 784232
Change-Id: Ic7eddd66b8fdd3f1680358842d135e0a45b857b0
Reviewed-on: https://chromium-review.googlesource.com/787010
Commit-Queue: Renjie Liu <renjieliu@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Jia Meng <jiameng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519935}

1. Allows reading ~/Library/Fonts (bug 786777)
2. Allows downloaded font access (bug 662686)


Bug: 786777,662686
Test: See crbug.com/786777 (comment 0 and comment 17) and crbug.com/662686
Change-Id: I3734f38bc72d8324dc482849e5a4bcb3238b88e5
Reviewed-on: https://chromium-review.googlesource.com/784473
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519934}

Avoided an extra string copy and used a move instead in
PrefService::Preference constructor.

Inlined some simple getters.
Added some const.

Change-Id: Id6a3027a34497e046c67838537ee18bbc541e891
Reviewed-on: https://chromium-review.googlesource.com/792371Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: François Degros <fdegros@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519933}

The origin_pid fields in request info structures were
used inconsistently: in some cases they stored a process
id, in other cases they stored a child_process_unique_id.

Neither PIDs nor child_process_unique_ids can be trusted
when received from a renderer process, so accepting either
value over IPC is somewhat dangerous. However, because
PPAPI network requests are still proxied though the
renderer process, we do need to some way to attribute
them -- the TaskManager being the sole consumer of that
information.

By switching to |plugin_child_id|, and eliminating other
uses of the origin_pid, we get to simplify the TaskManager,
remove some cruft, and allow the SiteIsolationStatsGatherer
to record PPAPI activity, which it already knows how to
classify.

Bug: 
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Id92e0ca2e95def6ed7924993c00b7ed56d0917c8
Reviewed-on: https://chromium-review.googlesource.com/738324
Commit-Queue: Nick Carter <nick@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519932}

ARC currently uses an unconventional surface hierarchy that diverges
from the Wayland model, but will align itself with upstream starting
with version 9. This CL extends the protocol to reimplement features
that relied on the surface hierarchy, e.g. expanded input region for
client-driven resizing.

Also, the compositor sets capture on the focused window during dragging
but not resizing. This CL adds a request to notify the compositor when
resizing starts.

Bug: b:67384524
Test: None
Change-Id: I991c94c9af525cee283f8d4f6b1fca21ff65bf7d
Reviewed-on: https://chromium-review.googlesource.com/794651Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519931}

Currently it's flaky that a partial buffer is read through network
pipeline when the first history db record is generated.

This CL changed the observer to be able to optionally wait for a
certain number of bytes read from network IO.

Bug: 788160
Change-Id: I110653433e8c80c2dabf9f3162df99d7bb354e86
Reviewed-on: https://chromium-review.googlesource.com/790946Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519930}

Bug: 
Change-Id: I6091760eb9f903bd2cbcf5c38dab954042b3268b
Reviewed-on: https://chromium-review.googlesource.com/794812Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Cathy Li <chili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519929}

This CL introduces a new enum that track the download source.

Currently it lives in content/public/browser, and passed in from
content::DownloadUrlParameters. In components/download, there is a one
to one mapping enum for usage in download in progress db, which can not
depend on content/public.

This enum is supposed to used in UMA as suffix for several key metrics
and UKM as Components, and saved in the new in progress level db.

Bug: 786482
Change-Id: I19a2f959eb9e7b0787087cad6c9519acbde13281
Reviewed-on: https://chromium-review.googlesource.com/777548
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519928}

Previously, there was two sets of mostly identical logic to start a trace,
ensure that heap dumps are collected, and then report the results.

Bug: 753218
Change-Id: I8dba3c94256a8da9e9364b49bd86275db14a9df3
Reviewed-on: https://chromium-review.googlesource.com/777554
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519927}

This allows CPanel to disable TLSv1.1/TLSv1.2 for compatibility with
buggy wifi APs.

BUG=605728
TEST=chromeos_unittests
TEST="sideload" an .onc file through chrome://net-internals and verify
     in the RADIUS logs that the TLSVersionMax setting takes effect
TEST=manually set value through shill and check in
     networkingPrivate.getProperties

Change-Id: I1c8447ca5f7c8b0c8ff3c4ce44be01955454d215
Reviewed-on: https://chromium-review.googlesource.com/789792Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Kevin Cernekee <cernekee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519926}

Update the in-product help text shown after pull-to-refresh. Also,
always show the pull-to-refresh IPH above the pull handle (rather than
the expand button when accessibility is enabled).

BUG=787030

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

staticText nodes will not work with the boundsForRange
function so it doesn't make sense to try to highlight
them.

Bug: 789211
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I958bb75e663f5cf2b073466014e7122899b892bf
Reviewed-on: https://chromium-review.googlesource.com/794517Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Katie D <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519924}

Bug: 786692
Change-Id: I5e5d2aaef1b6e9abfc20a752df67a8eedb8a5c07
Reviewed-on: https://chromium-review.googlesource.com/791535Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519923}

Using wpt-import in Chromium 33ce2fff.

Build: https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/6435

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
meade@chromium.org:
  external/wpt/web-animations

TBR=rbyers

No-Export: true
Change-Id: I162313170a602f89d29e3cea5a096e98befb0850
Reviewed-on: https://chromium-review.googlesource.com/794045
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#519922}