GitLab

Before this CL, we allowed 3 retries for the entire connection flow,
which includes advertising, scanning, creating a GATT connection, and
exchanging messages. However, it makes more sense to think of this as a
two-part process:
  (1) Advertising and scanning. This portion always occurs when
      attempting a BLE connection, even if the device we're trying to
      contact is not nearby and cannot respond.
  (2) Creating a GATT connection and exchanging message. This portion
      only occurs when an Android host is nearby to respond to the
      Chromebook.

Connection attempts which fail in part (2) above indicate that the
device actually is nearby and can potentially connect; additionally
connection failures during this part of the connection often will
succeed on a retry. Thus, this CL adds extra connection retry attempts
if a previous attempt failed in part (2).

Bug: 805218, 672263
Change-Id: Ifbedc004b96905d3f77662c45bcf2a9210b06c57
Reviewed-on: https://chromium-review.googlesource.com/889991Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533073}

Fullscreen low power mode (which is triggered by use of AVFoundation)
is causing 10.11's WindowServer to crash.

Bug: 806506
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: I40cfdfbd932be56cf0078c91cad824ee6895f9b6
Reviewed-on: https://chromium-review.googlesource.com/892097Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533072}

ExabyteResponse  is almost never ending response (with an Extabyte
content-length). This response will be used in iOS tests, so it is useful
to make it default.

Bug: 614168,789585
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ie0edb7bbfc427bb83dc8bfbc9e143d1cd0e890e7
Reviewed-on: https://chromium-review.googlesource.com/890300
Commit-Queue: Eugene But <eugenebut@chromium.org>
Reviewed-by: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533071}

Require an enum to be passed to Platform::CreateThread specifying the
type of thread which is requested to be created.

This allows recording metrics around thread cpu usage.

R=haraken@chromium.org,hajimehoshi@chromium.org,nhiroki@chromium.org
BUG=776416

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ie1855c52ab2259738fdc91ad3af89c476904c7bf
Reviewed-on: https://chromium-review.googlesource.com/888920
Commit-Queue: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533070}

These cases were discovered whilst adding a deprecation warning for the use of
'#' symbols in data URI bodies. For a '#' to exist inside the body, it must be
escape as '%23'.

Bug: 123004
Change-Id: If2e52db6c86d2610ecd0d4e175644494e18f47fc
Reviewed-on: https://chromium-review.googlesource.com/889718Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533069}

This CL moves Java TextSuggestionHost to be managed by
WebContentsUserData so ContentViewCore doesn't have to keep
a reference to the object, and the object can be obtained
easily by TextSuggestionHost.fromWebContents(). It helps
decouple the class from CVC.

Bug: 789000
Change-Id: Iefdeb0a727fc975323b7f8f24d4eb187ad38601b
Reviewed-on: https://chromium-review.googlesource.com/892180Reviewed-by: Ryan Landay <rlanday@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533068}

With a MDCButton, the font should not be set on the title label, but on the
button itself, using:
-[MDCButton setTitleFont:forState:]

Bug: 803767
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I4232f2d080daca4e8fc2e585d51c24c1b10ab1ac
Reviewed-on: https://chromium-review.googlesource.com/891221Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533067}

Adding the line to enable automatic bug filing for when WPTs are
pulled from upstream into the xr folder and are failing.

Change-Id: Idc24b4d610ceaa706c7d7fe12a35a8ff39775b43
Reviewed-on: https://chromium-review.googlesource.com/875249Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Anna Offenwanger <offenwanger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533066}

- Use base::BindOnce instead of base::Bind.
- Add ShutdownQuicTestServerDispatcher to trigger network errors without shutting down the server.
- Don't spam test log with bidirectional_stream state.
- Fix lint warnings.


Bug: 714018
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I4baf1f1e8718d4b5cc21f5664ee2dd1cc0bfa83d
Reviewed-on: https://chromium-review.googlesource.com/890058
Commit-Queue: Misha Efimov <mef@chromium.org>
Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533065}

Bug: 734093
Test: None
Change-Id: I49be629d3d0afe2e329fd4fada263d7746e23e5e
Reviewed-on: https://chromium-review.googlesource.com/892287Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533064}

This doesn't require special support, since the java.lang.reflect API allows
calling static methods the same way as instance methods.

Bug: 794320
Change-Id: Id9064ec69b6cbdbe23576fa1f3e5d5e0e2c30677
Reviewed-on: https://chromium-review.googlesource.com/894465Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533063}

 - Update the toolbar shadow and use alpha animation instead of
   transition drawable for url focus
 - Fix composited url bar alpha to prevent C++ url bar background
   from being drawn
 - Remove top padding in suggestions list when modern is enabled

 BUG=803088,803618

Change-Id: I848c1168ef26955a2eeb9b81738941f5fa886dd4
Reviewed-on: https://chromium-review.googlesource.com/893530
Commit-Queue: Theresa <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533062}

Also convert net::FileStreamContext to use it, as a sample use case with
few consumers.

This CL does not add a OnceCallback version of TestCompletionCallback,
as the repeating version works for use with methods that take
OnceCallbacks.  I think not creating a new test class will make updating
interfaces take a lot less effort.

Also, I expect that all net::CompletionCallbacks are effectively used
as OnceCallbacks, so we can make TestCompletionCallback return
OnceCallbacks when/if we ever finish converting all of net to use
CompletionOnceCallbacks.

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

The DCHECK in SVGElementProxy::IdObserver::ContentChanged() is too
restrictive. The document is only vulnerable to mutation during paint or
pre-paint, but should be safe to mutate once the update is done.

BUG=807159

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: If9f795e0ac55d204d5f165221af2453b54eda6a5
Reviewed-on: https://chromium-review.googlesource.com/894189Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533060}

This change adds new and improves existing code instrumentation for
tracing reports. They should help both with performance tracking and
memory usage investigation.

Bug: 806137, 793109
Change-Id: I45fd4ef567e83c174d09cf41424a961c13adaf23
Reviewed-on: https://chromium-review.googlesource.com/888087
Commit-Queue: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Yafei Duan <romax@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533059}

As a follow-up CL to the hot fix
https://chromium-review.googlesource.com/876528, this newly added unit test
verifies whether canvas restores its matrix clip stack after the image is drawn
from old canvas2d bridge to the new canvas2d bridge.

Bug: 803950
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I129525cad9835f415ac594351ba720d48c63979d
Reviewed-on: https://chromium-review.googlesource.com/888093
Commit-Queue: Olivia Lai <xlai@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533058}

Bug 764519 was fixed so relevant disabled tests are now enabled by this commit.

Bug: 764519
Change-Id: I1af80b6ecbbf9548aeae8d5ab08641180dde9f2c
Reviewed-on: https://chromium-review.googlesource.com/894263Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533057}

This CL just removes some includes that aren't used.

CrOS-style shadows are planned for more parts of the Chrome UI - parts
the window manager doesn't have good control over. So some files may
need to move.

Bug: 801583
Change-Id: I1a5a31908ae74ce373198e16dfa2809d4d60023a
Reviewed-on: https://chromium-review.googlesource.com/892585Reviewed-by: David Reveman <reveman@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533056}

https://chromium.googlesource.com/angle/angle.git/+log/13fd988cf71d..bd6ae4aa145d

$ git log 13fd988cf..bd6ae4aa1 --date=short --no-merges --format='%ad %ae %s'
2018-01-29 geofflang Vulkan: Don't create zero-sized textures.
2018-01-29 geofflang Vulkan: Allow dEQP to create Vulkan displays.

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: Id9edf6124da72fb34024573b59d68f20311f7d54
Reviewed-on: https://chromium-review.googlesource.com/894266Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533055}

Test: unit_tests AboutFlagsHistogramTest.CheckHistograms
Bug: 782320
Change-Id: I9b75d6e9b9e018b86a8d011653f02887e2a68f1e
Reviewed-on: https://chromium-review.googlesource.com/889920
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533054}

This may happen if children acquire scrollbars.

Change-Id: Iafd48e0f1afc927e8723f3a2f57b6dddf3157fd1
Reviewed-on: https://chromium-review.googlesource.com/889904Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533053}

This CL fixes a comment about scaling. In the process of making that
several presub/lint adjustments were also made.

(code health)

Bug: None
Change-Id: I29b2f8ad2260aa303be22135248978f97ff5abc8
Reviewed-on: https://chromium-review.googlesource.com/889990Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533052}

Removes .tentative extension from CSSUnparsedValue WPT.
Also adds a interface IDL test, which is currently failing because
Blink doesn't implement Array.values.

Bug: 774887
Change-Id: Ia59af546f72a1a664e16cb708dce3e97dfec75ea
Reviewed-on: https://chromium-review.googlesource.com/892583Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533051}

The delegate used to create separate code paths in ContentVerifyJob,
which makes the code harder to read and also creates a parallel
reality in tests. Remove it entirely since tests using the delegate
can work with the TestObserver in ContentVerifyJob.

Remove two tests: ContentVerifierTest:FailOnRead/FailOnDone, that
heavily used the TestDelegate. These tests were *artificially*
(different from how production code does) creating error conditions
from ContentVerifyJob::BytesRead and ContentVerifyJob::DoneReading.

Extract test utilities related to content verification to a
separate file (e/b/content_verifier/test_utils.h)

Bug: 796395
Change-Id: Ib59e9f0c7a4aac9b6a883d7f42647cecc603fa79
Reviewed-on: https://chromium-review.googlesource.com/888327
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533050}

Previously, it was querying the StatisticsRecorder
directly, which is not recommended. Use the HistogramTester
helper class which is exactly for this purpose.

Bug: None
Change-Id: I820716f31a96c31540cea14576db616361c63f96
Reviewed-on: https://chromium-review.googlesource.com/894489Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533049}

Remove using very specific names like whitelist/blacklist.  Make file and code
names more generic where it should be.

TBR=dcheng@chromium.org
TEST=chrome_elf_unittests.exe, ThirdParty*

BUG: 769590
Change-Id: I9f4d43825b1ba256ff18061b69ecba070d62c975
Reviewed-on: https://chromium-review.googlesource.com/890118
Commit-Queue: Penny MacNeil <pennymac@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533048}

Remove and destroy reflectors before closing and deleting hosts.
(roughly: hosts own the surface that reflectors use for painting)

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

Previously, the utility that tried to determine if the keyboard was
showing used a magic number (100 dp). Despite what the code implies,
this number accounts for both the top and bottom Android controls on
screen -- status bar and bottom navigation controls. On notched
phones the status bar is considerably larger; when added to the bottom
controls, the logic breaks. This change updates the logic to determine
the height of the status bar and does a best-effort to get the height
of the bottom Android controls. If the difference in height of the
app's viewport and window size is greater than the combined height of
the controls, the keyboard might be showing.

BUG=805030

Change-Id: Ie923549a0c6bcc0067f8d784250fbf273125bff9
Reviewed-on: https://chromium-review.googlesource.com/884829
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533046}

This CL allows XR30 for GpuMemoryBufferVideoFramePool output
format in Linux (not CrOs yet), and teaches GLImageMemory how
to manipulate this format.

Unittests are extended, tested also with high bit depth
videos e.g.:
'http://crosvideo.appspot.com?codec=vp9.2&loop=true'
and media/test/data/...
- bear-320x180-hi10p-vp9.webm
- bear-320x180-hi10p.mp4 (this is an H.264 part 10, 10bpc)
- blackwhite_yuv420p_hi10p.mp4
- bear-320x180-hi12p-vp9.webm

Bug: 803975
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: Ie5fb3fa60036591fabdfcf774fcb0878b1ebca07
Reviewed-on: https://chromium-review.googlesource.com/881665
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533045}

Change-Id: If1376c69b262c9112f8c3653feffebe961bd92b6
Reviewed-on: https://chromium-review.googlesource.com/894487Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533044}

We want multiple instances of these pages with different flags e.g.
sw raster and gpu raster in the new rendering.desktop/mobile page sets.

BUG=760553

Change-Id: I48e2ac82a4314cdf36a61f301559160b8d801f52
Reviewed-on: https://chromium-review.googlesource.com/887798
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#533043}

These metrics don't work well at the ServiceWorkerControlleeRequestHandler
layer for S13nServiceWorker, for the reasons in the bug. Actually they are
pretty suspect for non-S13nServiceWorker too because we are recording them on
every URL request, not just committed page load, so we are double-counting on
redirects.

This patch:
1) Moves the PageTransition metric to ServiceWorkerPageLoadMetricsObserver.
This is a better fit also because page transition info is expected to be
removed from ResourceRequest as per the TODO there.
2) Removes the RedirectChain metric. We haven't been using it. If needed
we can always add one to ServiceWorkerPageLoadMetricsObserver alongside
PageTransition.

R=bmcquade, kinuko

Bug: 805805
Change-Id: I58029612f8c7697ec280bcc80bec97f6f64d9dd9
Reviewed-on: https://chromium-review.googlesource.com/886102Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533042}

restore_session.html uses push/replaceState to restore URLs. This
technique doesn't work for app-specific URLs because they can't be
loaded natively by WKWebView. Restoring them as placeholder URLs reuses
the same code path for rendering WebUI and native view on back/forward
navigations.

Manually tested the session restore behavior and verified that history
with multiple entries are restored correctly.

Bug: 807102
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I9dd04f75dc464d645d30fe7c339e2ffe147b5fed
Reviewed-on: https://chromium-review.googlesource.com/894126
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533041}

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I67abbd6195ba728d5b1df29462eca2fa1857a58b
Reviewed-on: https://chromium-review.googlesource.com/887403
Commit-Queue: Misha Efimov <mef@chromium.org>
Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533040}

https://skia.googlesource.com/skia.git/+log/4e95956f117f..51494f6615b8

$ git log 4e95956f1..51494f661 --date=short --no-merges --format='%ad %ae %s'
2018-01-29 halcanary SkQP: Allow checking against nearby pixel's expectations.
2018-01-30 jvanverth Reduce the amount of padding needed for SDFs, take 2
2018-01-30 halcanary SkQP: remove skia_embed_resources option
2018-01-30 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 13fd988cf..513bc77df (1 commit)
2018-01-30 halcanary SkQP: slim deps.  Also skia_enable_fontmgr_empty
2018-01-29 scroggo Simplify SkAnimatedImage

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.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.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
TBR=bungeman@chromium.org

Change-Id: I5d556430c393f4a57138d11aeafeeab46f0ff126
Reviewed-on: https://chromium-review.googlesource.com/894190
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533039}

Change-Id: Ia3a268d031a9696c159d4c4605c2a44bd5e37a10
Reviewed-on: https://chromium-review.googlesource.com/894105Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533038}

All other accesses of bound_instance_ in this file check if the pointer
is null before using it. This appears to be an oversight.

Bug: 803391
Change-Id: Iaba41bf8e676696a9c7db9bcd327c6125da8c4ed
Reviewed-on: https://chromium-review.googlesource.com/877202Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Raymes Khoury <raymes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533037}

font-variation-settings shipped to stable in M62.

The CSSVariableFonts feature flag is no longer needed.

BUG=669453

Change-Id: I3061318331dda4f12a325caea49296b64cd8a05f
Reviewed-on: https://chromium-review.googlesource.com/892759Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533036}

As first seen in bug 799092, the AudioWorklet trial uncovered problems where
[OriginTrialEnabled] interfaces were not being exposed for module scripts in
worklets.

The root cause is that WorkletGlobalScopes are defined to have a unique, opaque
origin. This defeats the trial token validation which requires both a secure
context, and that the origin for the context matches the origin in the token.

For the purposes of origin trials, we believe it is sufficient to consider the
context of the document that created the worklet. If the document is secure, and
has valid token(s), the origin trial should be enabled. Analogous to this thread:
https://github.com/whatwg/fetch/pull/527#issuecomment-335677387

This CL changes so that any tokens from the document are passed along to the
worklet, and the origin of the document is used to validate any tokens. This
applies to all types of worklets, although the problem was initially found for
AudioWorklet.

As well the AudioWorkletProcessor interface has the [OriginTrialEnabled]
attribute reinstated (was removed in a previous CL as a short-term workaround).

Bug: 799960
Change-Id: I98cca05a7710e463a10dcd8c17f302f311f531b3
Reviewed-on: https://chromium-review.googlesource.com/862257
Commit-Queue: Jason Chase <chasej@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533035}

https://webrtc.googlesource.com/src.git/+log/cf30d8b1ec22..1a2f20748581

$ git log cf30d8b1e..1a2f20748 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-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.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Id30233f73403779d43d29c02479dedb41f28c4d9
Reviewed-on: https://chromium-review.googlesource.com/894127
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#533034}