GitLab

Before this CL this behavior is possible:
- a credential is autofilled.
- user removes the credential via settings or "Manage passwords" bubble.
- user clicks "Login" or reloads the page. In other words makes an action that we consider a successful form submission.
- password manager updates the credential in the store by reviving it.

After this CL the password manager is informed as soon as the password is removed. Thus, the copy of the credential in the memory should go away.

Bug: 821763,841853
Change-Id: If6c371312a9ed55217f5998989dd0457296a538a
Reviewed-on: https://chromium-review.googlesource.com/1064118Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559539}

This CL disables "Yes, I'm in" button, account picker and Settings link
in the streamlined sign-in screen if either account selection is pending
or sign-in is in progress or account list isn't available because of
a GMS error.

Bug: 814728
Change-Id: Ic5aa09395557268a7264d876b08e5b63197e85ee
Reviewed-on: https://chromium-review.googlesource.com/1062565Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559538}

crbug.com/546165 and crbug.com/546167 will be closed as WontFix, per
suggestion from net team here: crbug.com/546165#c8 and during another
codereview here: crrev.com/c/1060646

Bug: 546165, 546167
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I058aa14616538b445ecfa702ba660e5640015721
Reviewed-on: https://chromium-review.googlesource.com/1062714Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559537}

This CL shows the cancel button when the omnibox is focused on portrait.
The omnibox can be focused and not the first responder when the user
taps the omnibox, display some suggestions, scroll the suggestions.
The correct check to know if the omnibox is focused is if it is showing
the popup or if it is first responder.

Bug: 836814
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I2d021154f033c81ddde731163c813eb850a973bd
Reviewed-on: https://chromium-review.googlesource.com/1064113Reviewed-by: Stepan Khapugin <stkhapugin@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559536}

This CL turns back the global crazy linker mutex to recursive,
in order to support cases where a library's ELF initializer
calls dlopen() recursively.

This prevents crashes when Chrome is loaded on some devices,
due to the fact that a system library is loaded (by mistake)
through the crazy linker, and that its code actually dlopen()
another system library that has such a rare ELF initializer
(see bug below for details).

Another CL will be used to better select which libraries
are loaded with the system linker though.

+ Add a regression tests where three recursive dlopens()
  are performed (see test_dl_wrappers_recursive.cpp and
  related sources).

+ run_tests.sh: Make regression tests less noisy by default,
  and add a ---verbose option to get back to the old chatty
  output during development.

BUG=843804
R=pasko@chromium.org, lizeb@chromium.org, agrieve@chromium.org

Change-Id: Ife05f4bf314ca168b06402a144de96f1c946e546
Reviewed-on: https://chromium-review.googlesource.com/1064112Reviewed-by: Benoit L <lizeb@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559535}

This test assumes that 3 tasks posted to the same sequence from the
main thread will be scheduled on the same worker. This is incorrect
because of this:

1. Worker #1: Runs a tasks and empties the sequence, without adding
   itself to the idle stack yet.
2. Posting thread: Posts another task to the now empty sequence.
   Wakes up a new worker, since worker #1 isn't on the idle stack yet.
3. Worker #2: Runs the tasks, violating the expectation that the
   3 initial tasks run on the same worker.

This CL fixes the issue by starting the pool *after* the 3 tasks
have been posted.

Bug: 844009
Change-Id: Idcc74e8bea90b94ecba8e3a52abc4091c89044b2
Reviewed-on: https://chromium-review.googlesource.com/1064016Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559534}

We plan to share the snap fling logic between cc and blink. But with the
dependency restrictions, we can only put the shared logic under cc/.
This patch moves the logic from ui/ to cc/, in preparation for blink to
use the same logic to make snap fling works there.

As cc/ doesn't accept blink::WebGestureEvent and blink::WebInputEvent,
we create GestureScrollType and GestureScrollUpdateInfo to pass in the
necessary messages.

Bug: 778259
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I0df8cf1002d51646404310ca50eb00a536e0b5d1
Reviewed-on: https://chromium-review.googlesource.com/1024198Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559533}

This change fixes the Bluetooth clusterfuzz presubmit script by updating
the setup to use the new location of the bluetooth-helpers.js file. This
file was moved to wpt/ to allow Bluetooth tests to be migrated to wpt/.

Bug: 841656
Change-Id: I7e83b90a1be86963ed36014861179dd281ae1fb8
Reviewed-on: https://chromium-review.googlesource.com/1063123Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559532}

TBR=ccameron@chromium.org

Bug: 843401
Change-Id: I455a0147729a473f95c9b9408fdfd4540240a81f
Reviewed-on: https://chromium-review.googlesource.com/1064018
Commit-Queue: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559531}

We basically use request completion time recorded in the render
process to calculate responseEnd defined in Resource Timing API. This
is problematic because the renderer main thread can be blocked for a
long time, and that is confusing users of devtools and Resource
Timing API.

This CL changes how to calculate responseEnd. With this CL, it will be
calculated based on the completion time recorded in the browser
process.

Bug: 824155, 835502, 843440
Change-Id: I990da586a86c420d21a8115d13e840f7c29d462e
Reviewed-on: https://chromium-review.googlesource.com/1053849Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559530}

These tests do pass on some bots, e.g. [1], and it's not clear why they
were being excluded. If there's a legitimate reason for them not to run
on Android, let's figure it out and get a bug filed.

Sheriffs: if this causes the tests to start failing on Android bots,
please file a bug with information about the error, put the exclusion
back and reference the bug.

Bug: 842698

 [1] https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/3343

R=kbr@chromium.org, thakis@chromium.org

Change-Id: Ia3735e9ce17759f62b823eb5df3907f00547786c
Reviewed-on: https://chromium-review.googlesource.com/1063833
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559529}

These tests do pass on some bots, e.g. [1], and it's not clear why they were
being excluded. If there's a legitimate reason for them not to run on Android,
let's figure it out and get a bug filed.

Sheriffs: if this causes the tests to start failing on Android bots, please
file a bug with information about the error, put the exclusion back and
reference the bug.

Bug: 842698

 [1] https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/3343

R=kbr@chromium.org, thakis@chromium.org

Change-Id: I6bbb04f101ce72636ba0d9c151551a42b0480281
Reviewed-on: https://chromium-review.googlesource.com/1063756
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559528}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5cc09ffc..ae4ee999

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Id8d80176f1726e7f8f2352adf8379fee263c23fc
Reviewed-on: https://chromium-review.googlesource.com/1064171Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559527}

This patch separates ReportingPermissionsChecker class in two, making it
clearer which parts belong on the UI and IO threads.  The Profile
creates an instance of the UI class on the UI thread, and then creates a
subsidiary IO instance, which is how ChromeNetworkDelegate actually
performs permissions checks.  The IO instance as a WeakPtr to the UI
instance, since it must delegate to the IO thread to actually perform
the check.  If the Profile starts tearing down itself (and by extension,
the UI instance), the WeakPtr will be invalidated.  But importantly, the
IO instance will still be well-formed, in case the network delegate is
trying any outstanding permissions checks.

Bug: 704259
Change-Id: I2b8d437c835a00a90d59aa7e3f39a49d83f511f2
Reviewed-on: https://chromium-review.googlesource.com/1059455
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559526}

Change-Id: I719ea936ce488c7f29c636be6d4892f3a2691170
Reviewed-on: https://chromium-review.googlesource.com/1064013Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559525}

Pass in a context for PrepareSendToParent(). Do ShallowFlushCHROMIUM()
directly at the callers of FlushPendingDeletes() instead of going
through ResourceProvider. And Finish() after destroying the
LayerTreeResourceProvider instead of in the destructor.

R=piman@chromium.org, chrishtr

Bug: 826886
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ic303e296a1c5eacb2b05a7134fb3e919ebd32a32
Reviewed-on: https://chromium-review.googlesource.com/1062591
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559524}

Bug: 827323
Change-Id: Iab50342f157c7f77b6df1d6e0748f78de5d55387
Reviewed-on: https://chromium-review.googlesource.com/1047210Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559523}

It is never used.

Also remove support for running as a standalone binary, which is also
unused.

This is more cleanup before landing tests.

Bug: 840380
Test: compiles, chrome --show-taps-app works with and without mash
Change-Id: Ib6c8e07ca12d1e12072f9af210355be7a12a2a86
Reviewed-on: https://chromium-review.googlesource.com/1062949Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559522}

As with gesture-pinch-zoom-scroll-bubble.html, it can fail as well as
crash.

Bug: 787924
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ib8adbfaed9a25c49026d1c969f81b49b62c29c14
Reviewed-on: https://chromium-review.googlesource.com/1062214Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559521}

This is supposed to only be used for policies that never saw the light
of day but occupy an id. In this case the id has to be kept empty but
we don't have to drag a ton of useless code around.

BUG=842342
TEST=Manual presubmit tests.

Change-Id: Ib07a266be1ad35ed291ac08cf881c6d69b6c22f1
Reviewed-on: https://chromium-review.googlesource.com/1063726
Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559520}

Migrate SubresourceFilterContentSettingsManager to the new
OnUrlsDeleted method and improve deletion of the setting that stores
whether the ui has been shown to only be deleted if all urls of
an origin have been have been removed.

Bug: 839798
Change-Id: I74a9ec6206a07f5925eee8de2a0790976aa09221
Reviewed-on: https://chromium-review.googlesource.com/1063727Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559519}

This ensures that any metrics recorded before the native
library is loaded and intialized are also actually committed.
(e.g. this would ensure that UMA like
Android.WebView.Startup.CreationTime.Stage1.FactoryInit is
properly recorded and available for analysis in dashboard)

BUG=817644

Change-Id: I3067842f34513912b9cd2e6ade91d7fc2aa24b34
Reviewed-on: https://chromium-review.googlesource.com/1061529Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559518}

Getter and setter provided are in tex coordinates

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;master.tryserver.chromium.linux:linux_vr
Change-Id: Ic5dbe403a44b28cce4e5c35a0690c501f62c168d
Reviewed-on: https://chromium-review.googlesource.com/1062366
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559517}

- Entry regarding coverage missing for some *_fuzzer.cc files.
- Note regarding coverage from child processes from the browser.

TBR=inferno@chromium.org

Bug: 821617,834781
Change-Id: I69a645e3b311ac9c160d878afd518706b3a000fe
Reviewed-on: https://chromium-review.googlesource.com/1063995
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559516}

Add support for using the plane overlay fences provided by the
GbmSurfaceless::ScheduleOverlayPlane() method to synchronize display of
overlays in Ozone-DRM. This also involves implementing the
GbmSurfaceless::SetUsePlaneGpuFences() method to control whether the
provided fences are used instead of the internally constructed
EGLSyncKHR object.

Since the PendingFrame in GbmSurfaceless owns (through GLSurfaceOverlay)
the fences used for that frame, some refactorings where required in the
frame submission code to keep the PendingFrame alive until the frame is
complete.

Bug: 828393
Test: ozone_demo --use-gpu-fences on Ozone-DRM
Change-Id: Id48485c55d7a31b01858ed5dbbf45815ac54c621
Reviewed-on: https://chromium-review.googlesource.com/1021514
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559515}

These tests do pass on some bots, e.g. [1], and it's not clear why they were
being excluded. If there's a legitimate reason for them not to run on Android,
let's figure it out and get a bug filed.

Sheriffs: if this causes the tests to start failing on Android bots, please
file a bug with information about the error, put the exclusion back and
reference the bug.

(This also enables it on a Windows and some Cast bots; it probably passes
on those too.)

Bug: 842698

 [1] https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/3343

R=kbr@chromium.org, thakis@chromium.org

Change-Id: I28c59b515fbbd757783ab7c8f54f84557b9c0c67
Reviewed-on: https://chromium-review.googlesource.com/1063729
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559514}

These tests do pass on some bots, e.g. [1], and it's not clear why they were
being excluded. If there's a legitimate reason for them not to run on Android,
let's figure it out and get a bug filed.

Sheriffs: if this causes the tests to start failing on Android bots, please
file a bug with information about the error, put the exclusion back and
reference the bug.

(This also enables the test on two chromiumos bots. Presumably it passes
there too.)

Bug: 842698

 [1] https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/3343

R=kbr@chromium.org, thakis@chromium.org

Change-Id: I4f3febe1247d12a3a19f4f1455bc8c841af52628
Reviewed-on: https://chromium-review.googlesource.com/1063830
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559513}

This allows running with the audio service in and out of process.

Bug: 843961
Change-Id: I205c1b78997f5cdf40705b8100d90fb08e176fd5
Reviewed-on: https://chromium-review.googlesource.com/1064063
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559512}

Exact same test is contained in WPT:
wpt/css/cssom/cssom-setProperty-shorthand.html

Change-Id: I930f6b9f1c43200392d7c9d120a5d9e58bd44b32
Reviewed-on: https://chromium-review.googlesource.com/1064065
Commit-Queue: Rob Buis <rbuis@igalia.com>
Reviewed-by: Chris Nardi <cnardi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559511}

This allows running with the audio service running in and out of
process.

Bug: 843961
Change-Id: Id756240c3e3dd3d45d4477f5ff85a35b7d13356c
Reviewed-on: https://chromium-review.googlesource.com/1064057
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559510}

The entry point to the preconnect predictor is in WarmupManager, that
correctly handles both the current and new predictors.

Initialization still needs to be triggered for CustomTabs, as it otherwise
happens after the first page load, which is too late for mayLaunchUrl() to be
effective.

Bug: 817784
Change-Id: I8dd9a7d41a508954151f7700d2e3fffa9ceb0320
Reviewed-on: https://chromium-review.googlesource.com/1059127
Commit-Queue: Benoit L <lizeb@chromium.org>
Reviewed-by: Alexandr Ilin <alexilin@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559509}

It may have unwanted side-effects in the Action Center and is really
a benign failure.

Bug: 841475, 837796, 734095
Change-Id: I61cc2736742a50de72fd5a5b9c87ae233ff9a5f0
Reviewed-on: https://chromium-review.googlesource.com/1061414
Commit-Queue: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559508}

Replaces LeftViewProvider abstract class with an ObjC protocol. Makes
LocationBarLegacyView support it directly.

This immediately allows cutting the LocationBarControllerImpl middleman
for left images, and also allows an ObjC object to accept left images
with UI Refresh.

Bug: 818637
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Id02fae26c98c8c2b2336728723c45194e9470694
Reviewed-on: https://chromium-review.googlesource.com/1057673Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559507}

Other possible username feature was not launched and now Password
Manager UI moved in completely different direction (manual fallbacks etc).
Since this feature would intervene with the current refactoring it is
time to remove it.

Removing is done according to comment:
 https://bugs.chromium.org/p/chromium/issues/detail?id=188908#c9.

PasswordForm::other_possible_usernames is left, since it's used for
sending username correction votes, all other parts of other possible
username feature are removed.

Bug: 831123, 188908
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I1650d8c37e5c03b20440f002ae7248d3fab40bc7
Reviewed-on: https://chromium-review.googlesource.com/1054674
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559506}

The tools menu disabled elements had the standard blue color.
This CL makes sure that they have the correct grey color.

Bug: 843939
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Iddbd9e8ea33d329cd5552d77d3acd54db9b5473a
Reviewed-on: https://chromium-review.googlesource.com/1064050Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559505}

Now a WebUI message handler. Still keeps the same UI
for now, but has potential to be more (see earlier patchsets)

Bug: 809820, 788270
Change-Id: I9e2de72540f152ad367098d8255492378bbb28a3
Reviewed-on: https://chromium-review.googlesource.com/890627Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559504}

This PR changes these functions to return TaskQueueWithTaskType
- MainThreadSchedulerImpl::DefaultTaskRunner()
- MainThreadSchedulerImpl::InputTaskRunner()
- MainThreadSchedulerImpl::IPCTaskRunner()
- IdleHelper::IdleTaskRunner()

so that we can know the task types posted to these main-thread task
queues, which didin't have any task-type information.

Bug: 841172
Change-Id: I7c463437af1dd5478cbbfd39bdc1626ef2e5c3b3
Reviewed-on: https://chromium-review.googlesource.com/1063670Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559503}

https://github.com/w3c/web-platform-tests/pull/10985 changed lint.py
and wpt-importer is now failing because of it:
https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/17652

chromium.patch did not apply cleanly, so the changes had to be rebased
on the new wpt version.	This was much easier within the	wpt repo
itself, so the patch is	changed	to apply within	the repo.

Bug: 843799, 843945
Change-Id: I1ed9895b2461243c38fea552706960a3b99db2b6
Reviewed-on: https://chromium-review.googlesource.com/1061458
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559502}

For Windows component builds it is necessary to explicitly share nested
classes if those need to be visible outside of the DLL. This change adds
such an export in order to get Chromium Windows builds with Perfetto
enabled to build.

Change-Id: Ia03383a641425e1eb690bb1f0a539473c83f9a32
Reviewed-on: https://chromium-review.googlesource.com/1063870
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Commit-Queue: Primiano Tucci <primiano@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559501}

Bug: 832666
Change-Id: I2f8104042ba7320998b306f7fdda05af9cf67086
Reviewed-on: https://chromium-review.googlesource.com/1064090Reviewed-by: Max Morin <maxmorin@chromium.org>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559500}