GitLab

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}

This CL is fixing the owners for subfirectories.
Since we remove alexei as owner for this folder,
we rely on a ui/owners to stamp fonts/render-text
related code.

Change-Id: I514ae10e54fe9f75229d25c428ac5e3b67534372
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947552Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721266}

Enterprise customers want to prevent websites from querying payment
methods. This change adds an enterprise policy for that.

Bug: 963906
Change-Id: I1253dcd0a3db3774d1cd74a0ca366f8f4fe3bf55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940709
Commit-Queue: Kasjan Siwek <kasiwek@microsoft.com>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721265}

Use 'use_color_pipeline' build flag to gate the build and run of
color_unittests.

Since the flag is false by default, remove the unittest from buildbots
for now.

BUG=1003612

Change-Id: Idff6eefb720269e15c60ca69335a5eb0533bd592
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947225Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Wei Li <weili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721264}

This test class was only used by a BrowserPlugin specific test which
was removed.

Bug: 533069
Change-Id: I614699cdf1acbd774eac1487511f41bc64593037
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944628Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721263}

TestChildOrGuestAutoresize has a parameter to determine whether to use a
BrowserPlugin code path. Since BrowserPlugin is being removed, we
remove this parameter and the supporting test code.

Bug: 533069
Change-Id: I5c7cde29b612eba62b14c2bafe9063a874fb15b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944608Reviewed-by: James MacLean <wjmaclean@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721262}

This is similar logic to what AwContents.java uses when creating a
popup.

Bug: 1030186
Change-Id: I0f207dae5ec53c0df68adb504544ec769534ce01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1947639Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721261}

This replaces a special case in Document.

Bug: 1029822
Change-Id: I73a281ffaf29ae5ff9acf4b20c9fb87fd6e2e96e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949066
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721260}

These callbacks are going away.

Bug: 1029822
Change-Id: I6871110447bfd6e7e90a059108dc8ef52b10d2d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948493
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721259}

This CL brings the longtasks API up to date with the recent changes on
https://github.com/w3c/longtasks/pull/78. It also adds WPT tests for
those changes. The changes are:

* containerType is "window", "iframe", "embed", etc. depending on the
type of the culprit browsing context container.
* containerSrc is now the 'data' attribute when the container is an
<object>.

Change-Id: I06f661968778e3bec433a1bfe758b4604df01557
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949146Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721258}

This CL refactors the implementation of the recovery component action
handler for Windows so that most of the code can be reused in the
future for macOS recovery component. It also adds a unit test.

This is trying to reland
https://chromium-review.googlesource.com/c/chromium/src/+/1946020
which failed on Linux with:

recovery_improved_component_installer.cc:94:11: error: no member named 'start_hidden' in 'base::LaunchOptions'
options.start_hidden = true;
~~~~~~~ ^

Bug: 1029953
Change-Id: I685963ed8b281d5709867c55b73617a121e7b78b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949224Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721257}

Showing file name and line in the output can be useful in searching the
file name directly from your IDE.

Bug: 1015236
Change-Id: If6f3ad0d4e84af9942e0e7d3b3fdb53925a391a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949106Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721256}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/240afdb1c43a..981da03f24d0

git log 240afdb1c43a..981da03f24d0 --date=short --first-parent --format='%ad %ae %s'
2019-12-03 vadimsh@chromium.org [lucicfg] Update from v1.11.6 to v1.11.12.
2019-12-03 ehmaldonado@google.com gclient: Remove annotated_gclient.

Created with:
  gclient setdep -r src/third_party/depot_tools@981da03f24d0

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@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:1030067
Tbr: agable@chromium.org
Change-Id: I491ffcdd0df43a0cf595602909d7263ff47b8d51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949430Reviewed-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@{#721255}

This implements behind a default disabled base::Feature a mechanism by
which cookies that were accessed recently enough (as specified by a
FeatureParam value) from an eligible context are granted legacy cookie
access semantics. A previous cookie access is considered eligible if it
allowed HttpOnly cookies, and was same-site (strictly for get, laxly
for set).

Bug: 1029099
Change-Id: Id7bea1ca37e2d1d97a4c8c836f07758c8e647e05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948233Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Commit-Queue: Lily Chen <chlily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721254}

Fixes: 1025869
Fixes: 1025806
Fixes: 1025810
Fixes: 1025815
Fixes: 1025816
Fixes: 1025817
Fixes: 1025822
Fixes: 1025826
Fixes: 1025828
Fixes: 1025830
Fixes: 1025832
Fixes: 1025838
Fixes: 1025848
Fixes: 1025852
Fixes: 1025864
Fixes: 1025868
Fixes: 1025869
Change-Id: Iff42f97056e8a78eb28784229b35a290436c82d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949182Reviewed-by: Anthony LaForge <laforge@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721253}

This reverts commit c812ddcd.

Reason for revert: underlying bug was fixed.

Original change's description:
> Add debugging for virtual MakeCurrent with no decoder.
> 
> Dump without crashing on Android if this happens.
> 
> Bug: 892490
> 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_optional_gpu_tests_rel
> Change-Id: I824a4f4b9f09d3267113d6384370acae059e1690
> Reviewed-on: https://chromium-review.googlesource.com/c/1266335
> Reviewed-by: Khushal <khushalsagar@chromium.org>
> Commit-Queue: Kenneth Russell <kbr@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#597385}

TBR=kbr@chromium.org,khushalsagar@chromium.org,piman@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 892490
Change-Id: I9e1abd626d85a794d37f1e38fa59cb6ee827e446
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_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929646Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Auto-Submit: Frank Liberato <liberato@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721252}

There should be no behaviour change.

Change-Id: I39333abd5ef6c5650c2bc7b333e08eb36c31ad8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946424
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721251}

This CL adds a class to collect data for Smart Charging.
The implementation of the class is not completed yet and will be changed
in future CLs.

Here is the design doc: go/cros-smart-charging-logging

Bug: 1028853
Change-Id: I4a2b491be0d6929859a2fce1cb9a9d6bf6db0ec9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940315
Commit-Queue: Thanh Nguyen <thanhdng@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Jia Meng <jiameng@chromium.org>
Reviewed-by: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721250}

There is an android bug where Bluetooth low energy scans do not return
results unless the app has fine location permission.  Coarse location
permission should be sufficient to that is what we requested previously.
This is transparent to the user therefore it seems appropriate to simply
request fine permission every time.

Bug: 1025420
Change-Id: I0cec63857aa2c553f3ccf59c2f62db67fd07a93d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1941200
Commit-Queue: James Hollyer <jameshollyer@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721249}

Bug: None
Change-Id: I8c19dce72cc631336002c5c979748ed78772046e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948512Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721248}

Other scroll types will still directly enqueue a scroll event.

Forced layouts may cause scroll offset changes that are undone
by later updates.

There is no spec that requires the current behavior as far as I can
tell. The CSSOM spec calls out that it should fire "when the viewport
or element is scrolled" [1]

[1] https://drafts.csswg.org/cssom-view/#eventdef-document-scroll

Bug: 988991

Change-Id: I4e4ebcf2c5bcba8111d73ebd0b2b8a037034caaa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928243Reviewed-by: Nick Burris <nburris@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#721247}