The code is dispatching a pointerover to the document element. This seems like an allowed upon thing. The interact.js code isn't liking that the target can be document. They are calling target.matches essentially expecting target is a Element but target is a Document which inherits from Node which doesn't have the matches function.

jsc456@ are you in contact with the author of this site and can you advise them to fix it?

I'm not in contact but I can try reporting it to https://github.com/taye
However, this error does not exist in the current Chrome browser (nor any other browser that I can see) I use interact.js in a project which is how I found this error so we test this frequently. It just appeared in Canary.

Able to reproduce the issue on the latest canary(61.0.3119.0) on Windows-10,Mac OS 10.12.5 and Linux Ubuntu 14.04..

This is regressed in M-59.

Last good build: 59.0.3062.0
First bad build: 59.0.3063.0

Changelog:
==========
https://chromium.googlesource.com/chromium/src/+log/05267be8219e262196306d78d7eade8083de7595..2275c1f6d1f074d065de4d0d1aef624f9fcefa66

chaopeng@: Could this be related to https://codereview.chromium.org/2784313002 

Note: Adding the stable blocker for M-59 as this is regressed in M-59 & just in case fix needs to be targeted for next stable(M-59) release or stable refresh thereafter. Feel free to remove the blocker if this should not be blocking.

Thank you!

Based on comment#1, I am removing stable blocker.

I think the difference is that we're sending mouse events occurring over a frame scrollbar to the #document now, whereas we didn't before. Firefox also does this so I think we're actually improving interop here, but strangely the error doesn't occur there. I can't actually get pointerover events to fire in Firefox at all, so perhaps they're not supported/working (MDN says they should though) and that's why the error isn't showing up?

As discussed I believe we should be sending these events to the document.documentElement chaopeng@ will prepare a patch.

Just updated to Chrome Version 59.0.3071.86 (Official Build) (64-bit) and console error now appears in production version. I'm guessing you already knew that but just in case.

Yup we have a plan to fix it in 60.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/13ecf25f878437df5e233a1f9e567aff56324aec

commit 13ecf25f878437df5e233a1f9e567aff56324aec
Author: chaopeng <chaopeng@chromium.org>
Date: Wed Jun 07 19:35:18 2017

Change hover element to HTML element when over root scrollbar

We previously set hover element to document when over root scrollbar.
In this patch we change it to HTML element.

BUG= 729140 

Review-Url: https://codereview.chromium.org/2922193002
Cr-Commit-Position: refs/heads/master@{#477728}

[modify] https://crrev.com/13ecf25f878437df5e233a1f9e567aff56324aec/third_party/WebKit/LayoutTests/fast/events/touch/gesture/gesture-tap-frame-scrollbar-expected.txt
[modify] https://crrev.com/13ecf25f878437df5e233a1f9e567aff56324aec/third_party/WebKit/Source/core/layout/LayoutView.cpp
[modify] https://crrev.com/13ecf25f878437df5e233a1f9e567aff56324aec/third_party/WebKit/Source/web/tests/WebFrameTest.cpp
[add] https://crrev.com/13ecf25f878437df5e233a1f9e567aff56324aec/third_party/WebKit/Source/web/tests/data/hover-root-scrollbar.html

Confirmed fixed for me at least. thank you!

The NextAction date has arrived: 2017-06-16