GitLab

This change fixes the comment to reference the correct variable name.

Change-Id: I01d580306e1b10caf10e14f57c6efd927be53638
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948958
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721306}

https://chromium.googlesource.com/angle/angle.git/+log/fc2dd45054bf..a5045ac36d17

git log fc2dd45054bf..a5045ac36d17 --date=short --first-parent --format='%ad %ae %s'
2019-12-03 syoussefi@chromium.org glslang.l: refactor extension checks
2019-12-03 syoussefi@chromium.org Automatically call flex/bison if necessary
2019-12-03 syoussefi@chromium.org Vulkan: Fix WaW same-layout image transitions
2019-12-03 jmadill@chromium.org Revert "Add new test runner harness."
2019-12-03 geofflang@chromium.org D3D9: Log the exact error code generated by D3D9 device creation.
2019-12-03 geofflang@chromium.org Skip flaky BlendMinMaxTest.RGBA16F/ES2_Metal.

Created with:
  gclient setdep -r src/third_party/angle@a5045ac36d17

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC geofflang@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1029091,chromium:1030192
Tbr: geofflang@google.com
Change-Id: Iac0bf0c85816b099675c835b087d28778d1a652e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949168Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#721305}

Remove WebContentsMainFrameObserver and use a new
RenderFrameHost::IsDOMContentLoaded() method instead to determine if a
frame has loaded the DOM content.

Bug: 1011819
Change-Id: I816999b12e2f811db5b760b290f32134b5937576
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940152Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#721304}

This CL cleans up old Mojo types for
service_manager::mojom::InterfaceProvider using
PendingReceiver, Receiver, and PendingRemote.

It also updates struct DocumentScopedInterfaceBundle from
document_scoped_interface_bundle.mojom and struct
ServiceWorkerProviderInfoForStartWorker from
service_worker_provider.mojom

Bug: 955171
Change-Id: I57459c96295dabf5137054daa30ec47ebd950361
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948580Reviewed-by: Luke Halliwell (slow) <halliwell@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#721303}

It's no longer needed after downstream update.

TBR=trivial

Change-Id: I3982fb71edd8b41c78e92e177ce1c7dc5a1015f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1904548
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721302}

This change converts QuotaDispatcherHost mojom interface client in
blink to use BrowserInterfaceBroker.

Bug: 936482
Change-Id: Ib4879ab100af2aaf69ee763cf2767fdd50ec2f3a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1824731Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/master@{#721301}

We are implementing a local search service using approximate string
matching for query search. Currently the approximate string matching
algorithm is implemented as FuzzyTokenizedStringMatch under

chrome/browser/ui/app_list/search/search_utils/

and we will need to migrate this function to a location that can be used
by the local search service (under chrome/services/).

This cl moves FuzzyTokenizedStringMatch, TokenizedString and all other
related string matching functions to //chrome/common/string_matching so
that they can be shared by current clients and also future local search
service.

Design doc for local search service: go/cros-search-service

Bug: 1018613
Change-Id: If5648bf3046d52dd92ab5479dd94916552a99786
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939128Reviewed-by: Thanh Nguyen <thanhdng@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jia Meng <jiameng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721300}

cr.ui.Tree has a default row style handler that applies inline style to
rows to indent them (depth * 20px) using CSS padding-inline-start.

files-ng requires (depth * 22px) of indent. Add a custom cr.ui.Tree row
style handler for the files-ng case. Apply the indent style to the

   .tree-row > .file-row

element. Also style its minWidth to be 12px after the row .item-icon to
account for the rounded CSS border style of .tree-row > .file-row [1].

Per the current row design: 6px padding + 20px more-icon + 2px gap then
20px item-icon + then the 12px I mentioned: totals 60px.

[1] if the directory tree is narrowed, the .file-row's round border can
be drawn over the .item-icon (or over any element to its left depending
on the tree width) if the .file-row has no minWidth style.

Bug: 992819
Change-Id: I9ec261846ccb7a7e09d907dfbf23b089279f3110
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946057Reviewed-by: Alex Danilo <adanilo@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721299}

Bug: 1021016, 1026862, 1028615, 1028772
Change-Id: I4408b981271ccc3d21e8fa06db1fd8b69e32e386
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949483Reviewed-by: Chris Mumford <cmumford@google.com>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721298}

Now that the build is updated to the latest SDK, Q-only methods/fields
accessed through reflection can be written without them.

Change-Id: I96f35a25b5f026db06c77838ebee2a312fe0d439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948007
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721297}

Update GetChromeUrlApiId() to use {WINDOWS|LINUX|OSX|ANDROID}_PLATFORM as
|platform_type|, based on the current platform, instead of CHROME_PLATFORM
being hard-coded.

This change also necessitates relaxing the check in
V4GetHashProtocolManager::ParseMetadata to expect permission-related
metadata to be present for each of the above, now platform-specific,
versions of the API_ABUSE list.

Bug: 1028642
Change-Id: I88f917f04368470b77eca647972883d859fdcbc9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945823
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721296}

Bug: 1017166
Change-Id: I627c576a322c5e701fad105659b213c415e32a40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940207Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721295}

https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/ac7755fac459..4bab6cb11c26

$ git log ac7755fac..4bab6cb11 --date=short --no-merges --format='%ad %ae %s'
2019-11-27 skau system_api: Register org.chromium.PrintersService

Created with:
  roll-dep src/third_party/cros_system_api

Bug: b:143242799
Change-Id: Ie7ced8e7e97219e3d86657a74870a2957bf9fbf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949029Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sean Kau <skau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721294}

When the device is physically used as a tablet (e.g. detached or
flipped), the keyboard shortcut to rotate the display should
behave as a request to lock the user orientation to the next
rotation of the internal display.

App windows are allowed to lock the rotation to a particular
orientation in tablet UI mode on the internal display only.
In this case, the shortcut should switch between the allowed
rotations if any, or do nothing.

For example:
- If a window locks the rotation to kPortrait, the shortcut should
  switch the user rotation lock between kPortriatPrimary and
  kPortraitSecondary.
- If a window locks the rotation to kPortraitSecondary, then the
  shortcut should do nothing.

BUG=925087, 1026398
TEST=Manually, Added a new test.

Change-Id: I34bf76a336ef81de4f1f5269843a3dd8c5efcd4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1892054
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721293}

This helps to create balanced shard maps. Specifically for weblayer bot, this will help
us add startup.mobile without unbalancing the shard maps.

Bug: 1026327
Change-Id: I8f5ebceba13cc6f7de8450389ecf59410425e1c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949239
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721292}

Callback should set result if it returned true.
Detected with "init_stack_vars = true".

Bug: 1030261
Change-Id: I9088a0ab498c44f9a765bf89361c91298d9458e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949643Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Commit-Queue: Vitaly Buka <vitalybuka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721291}

https://swiftshader.googlesource.com/SwiftShader.git/+log/8ffeadb66ea7..fca575e9fa48

git log 8ffeadb66ea7..fca575e9fa48 --date=short --first-parent --format='%ad %ae %s'
2019-12-03 chrisforbes@google.com Regres: Add pending deqp change to fix bad graphicsfuzz tests

Created with:
  gclient setdep -r src/third_party/swiftshader@fca575e9fa48

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: Ica762341c58e6ad5a25beb37b6042c71865c012d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949583Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#721290}

- An End License User Agreement (EULA) link will be displayed to users
  in print preview if the printer they have selected requires a EULA.
- Adds a browser test to reflect this change.
- This CL will have a follow up to actually get the EULA URL from the
  Printer object.

Bug: 1023589
Test: Browser Tests + end to end manual
Change-Id: Iadffddf148eb13bc95687532ed66b9e2215ff3c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929089
Commit-Queue: jimmy gong <jimmyxgong@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721289}

This CL fixes tests that will be broken by
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1889351

Bug: 963183
Change-Id: I3af9e90385d38fd9f9dce6c8107de41afda03db3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1811968Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Jack Lynch <jalyn@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#721288}

Disabled due to flaky failures.

TBR=aleventhal

Bug: 1030507
Change-Id: I4d998a5b0175b07bcf31bbf385fc352b2d3d5521
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949558Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721287}

Bug: 1026327

Change-Id: Ia6a81e063cee197e3487bc408ac2456465c67751
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948236
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721286}

Issue: 1021698
Change-Id: I4ce164922f1e5f33c127a1e61602682f4cdcca13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949666Reviewed-by: Andrew Xu <andrewxu@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721285}

This is the last major patch to remove the use of direct blob interfaces
from IndexedDB code.

It removes BlobDataHandle from IndexedDBBlobInfo.  There's no longer
any need to load blobs on the IO thread as all the IndexedDBBlobInfo
can be created directly on the idb task runner.

The downside is that tests become a little bit more complicated because
asking for the uuid is asynchronous.

Bug: 1022214
Change-Id: I4bd07cf687b10a0c65efda2044e11bb88171d632
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947388
Commit-Queue: enne <enne@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721284}

AppServiceAppWindowCrostiniTracker is added to handle Crostini app
window special cases, e.g. CrostiniAppDisplay, Crostini shelf app id,
etc.

AppServiceAppWindowCrostiniHelper implements part of functions from
CrostiniAppWindowShelfController.

Update Crostini's LaunchApplication and CrostiniAppRestartView::Accept
to use AppServiceAppWindowCrostiniHelper.

BUG=1011235

Change-Id: If8f71b7b45e190431b1023fe9f1feab746f788f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941539
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721283}

This lets us use the JSON reader from base directly.

Change-Id: Ic0db4ace1c3f2b652a6af148e3eddc06df5282fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947983
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721282}

Using wpt-import in Chromium 9e1e5d01.
With Chromium commits locally applied on WPT:
500a74f5 "Add a runtime flag to enforce strict MIME type checks for workers."
a2a91a99 "Allow another touch start happen when there are active touch points"
85b61e6b "[resource-timing] Ensure workerStart is protected by TAO"
a75430aa "Fix appcache tests."
a50e7e60 "Move `Sec-Fetch-User` to SetSecFetchMetadataHeaders."
b0b9a76a "Revert "[LayoutNG] Set ShrinkToFit when determining MinMaxSize via layout""
83e4a43b "Refactor VRPose to fit better with WebXr concepts"


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:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa

No-Export: true
Change-Id: Icd00409937d0f18d89c68c1fb7735ba74961eca4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949346Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#721281}

Bug: b/145612776

Change-Id: I1c3f084c11e996d752b4eeed7ceb5750bcbe708f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947482
Commit-Queue: John Bauman <jbauman@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721280}

Every volume type in FilesApp has volumeMetadata from chrome.FMP, that
contains an iconSet property: it is empty (contains no icons) for most
volume types.

Somes volumes like AndroidAppItem, PROVIDED, and DOCUMENT_PROVIDER can
(and usually do) provide icons in the iconSet property. If they don't,
FilesApp draws nothing in their .tree-row .item-icon element today.

AndroidAppItem volumes can provide icons: in the files-ng case, draw a
generic provided icon if their iconSet has no icons.

VolumeItem PROVIDED and DOCUMENT_PROVIDER can provide icons, but there
is no reliable way to detect/fix their missing icons today since other
volume types use VolumeItem too. If they don't provide icons, FilesApp
files-ng will now draw a gray box in their .item-icon, a visual change
in behavior compared to normal FilesApp.

Bug: 992819
Change-Id: I6d2ec07ef91fd3acd8edff8bc5053eab4450680c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945958Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Reviewed-by: Alex Danilo <adanilo@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721279}

The permission wizard had a multi-purpose "Next" button whose text and
behavior were adjusted, depending on the wizard state. Resizing the
button sometimes caused rendering glitches in the bezel outline.

This CL simplifies things by creating separate buttons (and event
handlers) for each purpose, and it shows/hides them instead of
replacing the title strings.

This CL also enables/disables the "Next" button (according to
permission grant state), so that the buttons don't jump around as much.
The "Open .. preferences" button and "Next" buttons remain visible, but
the user can still only advance when permission is granted.

Bug: 1015201
Change-Id: I255fcc8bc3f8c18acfef0dc830964c40dd081e98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949673
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721278}

This reverts commit 548b6a4e.

Reason for revert: Suspected cause of failures seen in
https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-google-rel/10070

Original change's description:
> Stages storing model features first then models for get models responses
> 
> This change updates the store in stages to ensure only one store update
> in flight at a time. It prioritizes storing the model features first
> and then stores the prediction models once that update is complete.
> 
> Bug: 1001194
> Change-Id: Ic2d0ccaf64b49ca934590e6b7d0051668e155016
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938192
> Reviewed-by: Tarun Bansal <tbansal@chromium.org>
> Reviewed-by: Sophie Chang <sophiechang@chromium.org>
> Commit-Queue: Michael Crouse <mcrouse@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#721238}

TBR=tbansal@chromium.org,sophiechang@chromium.org,dougarnett@chromium.org,mcrouse@chromium.org

Change-Id: Iac2e56a8f949d30c93da1699dfb53ef15747c078
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1001194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949724Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721277}

Previously, when navigating from the left hand nav in the narrow window
size, focus did not move properly to the correct section since the
drawer closing causes focus to move to the full settings page. By
delaying the route change until the drawer closes in the narrow case.

Fixed: 1026019
Change-Id: I280c9b91660221a7363baf2e0a914002bdb31fbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929980
Commit-Queue: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721276}

https://pdfium.googlesource.com/pdfium.git/+log/8a0f76d3749e..3d7ad5ed37c1

git log 8a0f76d3749e..3d7ad5ed37c1 --date=short --first-parent --format='%ad %ae %s'
2019-12-03 thestig@chromium.org Roll third_party/freetype/src/ 3aaae716b..551bd3a90 (10 commits)
2019-12-03 tsepez@chromium.org Handle codepoints outside BMP in CFXJSE_FormCalcContext::Encode().

Created with:
  gclient setdep -r src/third_party/pdfium@3d7ad5ed37c1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pdfium-autoroll
Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: chromium:1029565
Tbr: pdfium-deps-rolls@chromium.org
Change-Id: I153d55e7f0fbe843537e21f2e824f6eeb37343ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949584Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#721275}

Updated an error message string to more accurately describe the WebXR
state needed to satisfy it, removed a couple of WebGL helper methods
that were only being called by WebVR previously, and removed a Gamepad
enum from the IDL that was WebVR-specific.

Bug: 1030470
Change-Id: I6a4a53240f761eed94100dd374c4504f28a99b98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949298Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721274}

Looks like there was a copy paste error with
IDS_ONC_TETHER_SIGNAL_STRENGTH_OKAY having the string "Weak" which was
incorrect

Change-Id: Ic0dbadc4fb34074a3fc633c2103e54bc7441abd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939686
Auto-Submit: James Vecore <vecore@google.com>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721273}

Bug: 1029175
Change-Id: I99956e145775cc5cc4a9b6f8f6a64a97c783442a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1938033
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721272}

Search and replace to spell "supported" correctly. Also fix lint errors
in modified files.

Change-Id: I4411bc2737f7ceb1b9cfa9c3316864d038a3afb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949022Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721271}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/84e94841f5ea..56f46565e9ed


Created with:
  gclient setdep -r src-internal@56f46565e9ed

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: I52703474b13478b05e9b5b2d00611a7ab4801da8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948949Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#721270}

Bug: 1021689

Change-Id: Ida4f922471b9e53684acfc683623150b82e2a7cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1906873
Commit-Queue: Charlene Yan <cyan@chromium.org>
Reviewed-by: Connie Wan <connily@chromium.org>
Reviewed-by: Taylor Bergquist <tbergquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721269}

VA-API is a linux-specific API. This CL adds the assertion that lets gn fail
if media/gpu/vaapi is built for neither Linux nor ChromeOS platform.

Bug: 1000575
Test: compile chrome
Change-Id: I71836047fe69bff28640297e58415983a97d6760
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847591Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721268}

We have a new component, Internals>Metrics>Tricium, just for Tricium bugs.

R=bpastene@chromium.org

Bug: 1030037
Change-Id: I093f2a684d2523c99bf1493084a9f85c24bf2507
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949302Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Auto-Submit: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721267}