GitLab

libva 2.0 is a major version upgrade, meaning that the library dlopen'ed
by Chromium is renamed from libva.so.1 to libva.so.2.

Due to the way ChromeOS is built, we may end up with a browser build
against the old libva even after the sysroot is upgraded to the new
version. For this reason we will keep both versions of the library on
the system until all buildbots have caught up to the 2.0 upgrade.

This patch makes Chromium capable of loading any of these two versions,
by whitelisting the newly-introduced libraries on the rootfs, and
loading the correct library depending on the version it has been
compiled against.

The old libva 1 paths will be removed once the buildbots have all caught
up.

BUG=chromium:785117
TEST=Made sure that the chrome binary and video_decode_accelerator_unittest
were both finding and loading the right library.

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: I3b24ffdd2ac9dcadacab2f3e10dbe62644e9ce01
Reviewed-on: https://chromium-review.googlesource.com/781324Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Wu-Cheng Li <wuchengli@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518595}

This CL implements skeleton view for the autofill on-field popup.
Every type of the autofill popup is displayed as a text row after this CL.
The implementation is guarded with a feature. Screenshots of some popups are
attached to the bug.

This CL doesn't implement animation related to the popup, e.g. the row isn't
hilighted when the mouse hovers over the row.

The separator element isn't displayed.

BUG=768881

Change-Id: Ib235a1b811ce0026428fdc03d1eba7f7be27fd0a
Reviewed-on: https://chromium-review.googlesource.com/685237
Commit-Queue: Tatiana Gornak <melandory@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518594}

This fix is similar to
https://chromium-review.googlesource.com/c/chromium/src/+/778648.

virtual/incremental-shadow-dom/shadow-dom/nodetree-radio-node-list.html should
be fixed with this CL, however, it still crashes due to crbug.com/787717.

Once we can rewrite built-in elements so that they don't use Shadow DOM v0
feature, the crash would be gone.

Bug: 776656
Change-Id: I0acde37be7688c9875cbbed633f3a527f91b66ed
Reviewed-on: https://chromium-review.googlesource.com/784740Reviewed-by: Takayoshi Kochi <kochi@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518593}

Site engagement entries are currently included in the cookie counter.
This creates an entry for every single site visited, which is
especially confusing when cookies are turned off. Site engagement
doesn't act like a cookie (it can't be read or written by a site), so
this CL removes it from the counter.

Bug: 782606
Change-Id: Ia0953b8a34b3899d19fe19af1da3c8ec21600f23
Reviewed-on: https://chromium-review.googlesource.com/774283
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518592}

Before this CL, ModuleScriptLoader::Fetch() sets the Referrer in
ModuleScriptFetchRequest after creating a FetchParameters instance. This doesn't
take effect.

This CL fixes it by updating the Referrer via
FetchParameters::MutableResourceRequest(). Also, this adds WPT tests for the
Referrer on module scripts.

Bug: 786862
Change-Id: Ib0031407796e1a7e701565094396e5442aa75702
Reviewed-on: https://chromium-review.googlesource.com/780479
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518591}

Makes callback functions return v8::Maybe so that the
call sites handle an exception if any.

Also this patch renames |call| function to |Invoke|.

For convenience, if the return type of IDL callback
function is void, the bindings code generator defines
|InvokeAndReportException| that captures and swallows
an exception if any.

If the return type of IDL callback function is not
void, the call sites must check the return value.
|InvokeAndReportException| is not defined in non-void
case.

Bug: 779036
Change-Id: I1057cb2fcd88208310f79e184aaf1b069a0f81f8
Reviewed-on: https://chromium-review.googlesource.com/768259Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518590}

WorkerScriptLoader is using UTF8 as a default encoding.
But currently ServiceWorkerInstalledScriptsManager is using latin1 as a default encoding.

Bug: 787736
Change-Id: I5a871fd87b994ad4d439f822e9254ca5df3af76b
Reviewed-on: https://chromium-review.googlesource.com/784741Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518589}

Before this CL, we installed conditional interface objects, i.e.
[SecureContext] attributes, on Window objects if and only if
the Window object was created from snapshot.
This CL installs them on the Window object regardless if it is
created from a snapshot or not.


Bug: 786750
Change-Id: I5166340b0d300b7101d5ec04a7f4a5212dd4e43b
Reviewed-on: https://chromium-review.googlesource.com/778642
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518588}

The current heuristics: if there is one button on a password form, let's
assume that this is the submit button. But some sites have many buttons in
a password form (for example show password). Let's improve heuristics:
if there are button[type='submit'], let's assume that this is submit
buttons (even there are multiple of them), otherwise let's fallback for
the initial heuristics.

Bug: 715717
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Idfe9d9f76e4e1ff5d80719db63fc2a0864f1e3bc
Reviewed-on: https://chromium-review.googlesource.com/781866
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518587}

The | at the end would match everything.

Bug: None
Test: None
Change-Id: If4ea72e4487571a0a7d40d6673fde4e85f604a8f
Reviewed-on: https://chromium-review.googlesource.com/784655Reviewed-by: Naoki Fukino <fukino@chromium.org>
Commit-Queue: Tomasz Mikolajewski <mtomasz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518586}

After S13nServiceWorker, clients can directly fire events without the browser
process, so we need to move some codes which tracks events to the renderer. This
patch is to implement the idle timer on the renderer.

In this patch,
- SWContextClient tracks the number of inflight events by using SWEventTimer
  which is added by this CL
- SWContextClient::OnIdle() is called when 30 seconds passed after the end of
  the last event, and it requests termination to the corresponding EWInstance
- EWInstance stops the worker, or do nothing if there are inflight events which
  are dispatched just before RequestTermination.

Even after moving the idle timer to the renderer, the browser still has the
primarily control of the lifecycle of the worker thread. If the worker thread is
unresponsive, the browser will detect it by a ping-pong timer and terminate the
worker thread.

Bug: 774374
Change-Id: I8d9cbb60cbf7583be3eb12a88860f74bbdcc949f
Reviewed-on: https://chromium-review.googlesource.com/758314
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518585}

Based on mojoms in issue 2882213002 (http://crrev.com/2882213002#ps1)

BUG=

Change-Id: I464d2178713a64f35aaec02e0ac365344b821cb1
Reviewed-on: https://chromium-review.googlesource.com/580988Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Commit-Queue: Oskar Sundbom <ossu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518584}

The interface is only used for decoding. I am going to remove the
usage from Android side. Before that, remove the check of the
parameter.

BUG=None
TEST=None

Change-Id: I0038f4971f8cd9afe429ff52ff395423d9c4548e
Reviewed-on: https://chromium-review.googlesource.com/778502Reviewed-by: Kuang-che Wu <kcwu@chromium.org>
Commit-Queue: Owen Lin <owenlin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518583}

Bug: chromium:780749
Change-Id: Ia9f7c7fb5f011e5f2af93421eb11787778a84ff9
Reviewed-on: https://chromium-review.googlesource.com/783211Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518582}

https://webrtc.googlesource.com/src.git/+log/2707fb2782e7..37e489c985ca

$ git log 2707fb278..37e489c98 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc
BUG=None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None


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
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Ie21536881887cb707bf52a55ae21dce25b98dfe3
Reviewed-on: https://chromium-review.googlesource.com/783840Reviewed-by: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Commit-Queue: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518581}

NewTabPageTest#testRender captures images of the New Tab Page at its
start position and when scrolled. It used to have a timeout checking
against the scroll position to ensure it was fully scrolled before
the second capture. With the condensed layout on larger screens there is
not enough space to scroll that far, so the test was failing with a
timeout.

This change instead requests that the RecyclerView scrolls to the
bottom and the criteria for the timeout is now whether the View can
be scrolled any further.

Bug: 784598
Change-Id: I696b08dfdae36209a6549141fa31006233dc17a9
Reviewed-on: https://chromium-review.googlesource.com/782120
Commit-Queue: Peter Conn <peconn@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518580}

This reverts commit 24d1491f.
 
Reason for revert: suspected in breaking  webkit_layout_tests
virtual/threaded/fast/scroll-behavior/smooth-scroll/ongoing-smooth-scroll-vertical-rl-anchors.html,
see
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/12398

Original change's description:
> Animation tests: Use rAF instead of setTimeout
> 
> With a debug build, a slow or busy machine, and a demanding animation
> (e.g. cross-faded images),
> setTimeout might wait indefinitely.
> 
> Using requestAnimationFrame is more effective.
> 
> BUG=248938
> 
> Change-Id: I8636b17123bb30ef675b8a3aa5cfe2e297aac222
> Reviewed-on: https://chromium-review.googlesource.com/784373
> Reviewed-by: Darren Shen <shend@chromium.org>
> Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#518561}

TBR=ericwilligers@chromium.org,shend@chromium.org

Change-Id: I823b5d060863a0a049ce447939b7e2a4570ad752
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 248938
Reviewed-on: https://chromium-review.googlesource.com/784950Reviewed-by: Olga Sharonova <olka@chromium.org>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518579}

Convert ITunesLinksObserver to directly track the registration
with the observed WebState instead of relying on the deprecated
code in WebStateObserverBridge.

Bug: 775684
Change-Id: Ia88fe44a99ed762d46894de95e18f8ebde18dd79
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Reviewed-on: https://chromium-review.googlesource.com/778999
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518578}

PowerManagementClient::Observer interface.

IdleEventNotifier is the class that will listen to all
relevant signals and emit idle events to its observers
after certain period of inactivity.

The overall user activity event logging sys will contain
two components:
(i). IdleEventNotifier
- This class is responsible for detecting when we should
start logging: we should start logging after an idle period.
- It will listen to multiple signals (power manager signals,
user activity, video activity etc) to determine whether idle
event has occurred, see
https://docs.google.com/document/d/123eFd0rUTu0140V6hJKkkWmpqibdIfM-zTtUR5a2qaQ/edit#
(ii). UserActivityEventLogger
- This class is responsible for feature extraction and
determining event types, and log the event. This will
be implemented as an IdleEventNotifier::Observer in
a later cl. Note, UserActivityEventLogger will also
implement other observers to listen to power management signals etc.

In this cl, we only implement PowerManagementClient::Observer
interface for IdleEventNotifier so that we can observe the following signals:
- Lid-opened
- Power-changed
- Suspend (SuspendImminent and SuspendDone)
We will add other interfaces to IdleEventNotifier in future cls.

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

There is a chance that VolumeReaderJavaScriptStream::Read() waits a response of
ReadChunk forever.
The problematic scenario is illustrated in
https://bugs.chromium.org/p/chromium/issues/detail?id=457448#c28

VolumeReaderJavaScriptStream can request ReadChunk without a client's request to
read ahead.
It expects a response through VolumeReaderJavaScriptStream::SetBufferAndSignal,
but a response can be ignored in Volume::Volume::ReadChunkDone() if the file for
previous Read request is already closed. This can cause Read() to be hanged.

Considering the case of reading ahead (without explicit Read requests from
client), I think we should always set buffer and signal
VolumeReaderJavaScriptStream when ReadChunk is done.

scrolling randomly.

Bug: 457448
Test: Open a zip file which contains 1000 photos, and browse photos by
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Iade702bf06042d9687f0a5793833d2486a3d761a
Reviewed-on: https://chromium-review.googlesource.com/784692Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Reviewed-by: Tomasz Mikolajewski <mtomasz@chromium.org>
Commit-Queue: Naoki Fukino <fukino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518576}

It is comparing size_t and enum w/o cast.

Bug: 778262
Change-Id: Iec0c159eae06c6450bdeb3f592106216071d797a
Reviewed-on: https://chromium-review.googlesource.com/784673
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518575}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/df985bbc..0001378a

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;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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

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

This patch adds synchronization to the sensorStarted and sensorStopped
methods to prevent races between the main thread starting and stopping
sensors and the sensor event handler thread processing a sensor error.

Bug: 780220
Change-Id: I9ff1f5e24ba59aaeddcda88ea8c63b6cf6f59287
Reviewed-on: https://chromium-review.googlesource.com/783705Reviewed-by: Alexander Shalamov <alexander.shalamov@intel.com>
Reviewed-by: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518573}

Embed requested resources into tests. This will allow verifying more
complicated redirect chains, and also keeping inputs and outputs together
makes them more comprehensible.

Bug: chromium:787197
Change-Id: I705e0d859ad2cca8b686ea3b6e09b0af182eee30
Reviewed-on: https://chromium-review.googlesource.com/781379Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Commit-Queue: Sergei Datsenko <dats@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518572}

Chrome UI had top/bottom browser controls that may shrink Blink's view size.
Previously all the info (control height, flag indicating that shrinking should
happen) are passed down to generate the view size upon request in content layer.

This CL moves the responsibility to embedder(Chrome) so that all the shrinking
happens before reaching content layer. With this CL, the view size stored in
ViewAndroid already the shrinking affect taken into account. The browser control
info are still passed but they are for plumbing, to be used in Blink/cc only.
The new shrinking logic lives in CompositorViewHolder/CompositorView that
already knows about them.

Now browser control update info is fetched through WebContentsDelegate
which is overridden per content (i.e. tabbed content, overlay panel content)
each of which has its own way of managing the info. Other embedders that do not
need dynamic browser control update will use the default implementation.

Related discussion is in the bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=622847#c30

Follow-up CL's will remove size logic still left in ContentView/ContentViewCore,
and also pull the browser control size info out of ResizeParams since they
don't have to be in frame-by-frame struct.

Bug: 622847
Change-Id: I8b7aa8ba0207b405b83a9c787ec2d8684f2b01fe
Reviewed-on: https://chromium-review.googlesource.com/752963
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518571}

From discussion on chromium-dev, it was decided to remove 'chrome'
namespace.

TBR=jam@chromium.org

Bug: 289619
Change-Id: Ie227e64bffecdaf115c5d2aba625d929e7550994
Reviewed-on: https://chromium-review.googlesource.com/781159
Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518570}

https://chromium.googlesource.com/angle/angle.git/+log/cce013c9b614..acf2f3adbac0

$ git log cce013c9b..acf2f3adb --date=short --no-merges --format='%ad %ae %s'
2017-11-21 jmadill Apply Chromium style fixes.
2017-11-21 jmadill Fix ComputeGenericHash.
2017-11-06 jiawei.shao ES31: Implement creation and attaching geometry shader on OpenGL
2017-11-21 jmadill Reland "Update cq.cfg for new compile-only builders."

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

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

Currently we use StrongBindingSet for mojo interface implementations
that needs access to MojoCdmServiceContext. Hence the lifetime of those
objects are determined and we should be able to use raw pointers instead
of weak pointers.

In MojoCdmService, MojoAudioDecoderService and MojoVideoDecoderService
we assume the MojoCdmServiceContext always exists.

In MojoRendererService, where it is currently also used outside of
MediaService (see RenderFrameHostImpl), it's possible that
MojoCdmServiceContext can be null, and we have explicit check on that.

BUG=786736
TEST=Existing tests pass.

Change-Id: Idd7e0a1bb24d109c7a17607e3fd856506432e9ee
Reviewed-on: https://chromium-review.googlesource.com/780046Reviewed-by: Frank Liberato <liberato@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518568}

window.event should be undefined if an Event's target is in a shadow
tree, because it is leaking information from inside the shadow tree.
But we don't know how frequently window.event is used for V0 Shadow DOM.

This change adds a use counter for window.event calls where the event's
target is in a V0 shadow tree,  so that we will know when usage is low
and it's safe to remove window.event for V0 Shadow DOM. Support for
window.event for V1 Shadow DOM is removed in crrev.com/c/773922

Discussion link: https://github.com/whatwg/dom/issues/334

Bug: 779461
Change-Id: Iadc734ebaeb90f44f832bcbe30f0ac9d0be1cff1
Reviewed-on: https://chromium-review.googlesource.com/780722Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518567}

This Cl adds a new AddressUnreachableURLLoaderFactory which fails to load
a given URL and will forward other URLs to the default url loader.

This CL also cleans up how we install test a URLLoaderFactory.

Bug: 769401
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I353e1ee5347f72c80a7c6c06a5ac859f40bc8690
Reviewed-on: https://chromium-review.googlesource.com/780769
Commit-Queue: Doug Turner <dougt@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518566}

Bug: 780378
Change-Id: I6b3bfd0afb9547b94c00f3617994c5ef8be72a89
Reviewed-on: https://chromium-review.googlesource.com/784555Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518565}

This converts internal Callback of SingleReleaseCallback from legacy
Callback to OnceCallback, so that the user can pass OnceCallback.

Bug: 771087
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: Ia91c8a7700610fa70b43b1b4d71c229c8f246079
Reviewed-on: https://chromium-review.googlesource.com/748342
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518564}

The existing current_keyboard_bounds() getter will simply return the
bounds as-is.

This CL introduces a second getter that will return the bounds that
block a portion of the workspace. If the keyboard is open but isn't
blocking the workspace (i.e. the floating keyboard) then empty bounds
will be returned.

Bug: 787713
Change-Id: I709bf4904d907336def32dfc73755ccb45422701
Reviewed-on: https://chromium-review.googlesource.com/784751Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Commit-Queue: Blake O'Hare <blakeo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518563}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/049f076ab6d2..7d9d9233cb65

$ git log 049f076ab..7d9d9233c --date=short --no-merges --format='%ad %ae %s'
2017-11-21 myjang [depot_tools] Add mock lib

Created with:
  roll-dep src/third_party/depot_tools


The AutoRoll server is located here: https://depot-tools-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.


TBR=phajdan.jr@chromium.org

Change-Id: Ib3fae0ec40da1b54db189dcd0616d2bd43688353
Reviewed-on: https://chromium-review.googlesource.com/784558Reviewed-by: depot-tools-roller . <depot-tools-roller@chromium.org>
Commit-Queue: depot-tools-roller . <depot-tools-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518562}

With a debug build, a slow or busy machine, and a demanding animation
(e.g. cross-faded images),
setTimeout might wait indefinitely.

Using requestAnimationFrame is more effective.

BUG=248938

Change-Id: I8636b17123bb30ef675b8a3aa5cfe2e297aac222
Reviewed-on: https://chromium-review.googlesource.com/784373Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518561}

This reverts commit 5e2df665.

Reason for revert: Suspect causing flaky ProfileShortcutManagerTest.
Bug: 787683

Original change's description:
> Add MOCK_TIME mode to ScopedTaskEnvironment :)
> 
> Taking advantage of the new kBoundToThread mode on
> TestMockTimeTaskRunner.
> 
> This change also required tweaking the
> ScopedTaskEnvironment::RunUntilIdle() logic as RunLoop().Run() on
> TestMockTimeTaskRunner results in advancing time when there's no
> request to quit-when-idle which is undesired here. New logic gets rid
> of need for |on_queue_empty_closure_| and I think is simpler overall.
> As of patch set 20, this new RunUntilIdle() logic also avoids using
> TaskScheduler::FlushForTesting() as that can result in hangs should a
> TaskScheduler task synchronously block on the main thread.
> 
> R=​fdoray@chromium.org
> TBR=gab@chromium.org (IWYU fixes)
> 
> Bug: 708584
> Change-Id: I76ba55ec64d398151420379d3fcdcd5186fbceb8
> Reviewed-on: https://chromium-review.googlesource.com/638550
> Commit-Queue: Gabriel Charette <gab@chromium.org>
> Reviewed-by: Gabriel Charette <gab@chromium.org>
> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
> Reviewed-by: François Doray <fdoray@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#518433}

TBR=khorimoto@chromium.org,gab@chromium.org,fdoray@chromium.org,robliao@chromium.org

Change-Id: I8a8822b221c73159f02297a6b7bdd60ddc5c49bc
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 708584
Reviewed-on: https://chromium-review.googlesource.com/784512Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518560}

This reverts commit 0af3ff20.

Reason for revert: Blocking revert of r518433.
Bug: 787683

Original change's description:
> Nits follow-up to https://chromium-review.googlesource.com/c/chromium/src/+/638550
> 
> R=​robliao@chomium.org
> 
> Bug: 708584
> Change-Id: I9c362e5cc3880644392cc6afcf4754d2fc834ea8
> Reviewed-on: https://chromium-review.googlesource.com/783873
> Commit-Queue: Gabriel Charette <gab@chromium.org>
> Reviewed-by: Robert Liao <robliao@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#518521}

TBR=gab@chromium.org,robliao@chromium.org,robliao@chomium.org

Change-Id: I832c5f3aba7073614fa331dc427d9ef0f1053f52
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 708584
Reviewed-on: https://chromium-review.googlesource.com/784571Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518559}

This will be generated on the java side and will be used to evaluate
the performance of handling the SafeBrowsing result on a helper thread.

This new API is used in a followup here:
https://chrome-internal-review.googlesource.com/509097

Bug: 786435
Change-Id: I2235eaf7ca900e326e3fbef45bede2d6a2c98d35
Reviewed-on: https://chromium-review.googlesource.com/777693
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518558}

Currently, the NTP override prompt only shows once per profile for any
NTP overriding extension installed. The NTP override prompt should be
displayed each time an NTP overriding extension is installed for a
profile. This CL implements such a change.

Bug: 748803
Change-Id: I896d9360a2a6e84f8586da481eb49be2428e9df0
Reviewed-on: https://chromium-review.googlesource.com/722454
Commit-Queue: catmullings <catmullings@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: catmullings <catmullings@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518557}

Bug: 774622
Change-Id: Ieb331d387b9e1f55eb0e2b8bec0c662918a2790a
Reviewed-on: https://chromium-review.googlesource.com/783523Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#518556}