Works in beta 60.0.3112.50

Does not work in dev 61.0.3142.0

What the bug looks like

Deleted: Screenshot_20170711-095450.png 583 KB

	Screenshot_20170711-095450.png 583 KB View Download

Thanks for the report!

Good build: 61.0.3137.3
Bad build:  61.0.3138.0
Regression range:  https://chromium.googlesource.com/chromium/src/+log/61.0.3137.3..61.0.3138.0?pretty=fuller&n=10000

Good commit: 481207
Bad commit:  481208
Culprit CL:  https://chromium.googlesource.com/chromium/src/+/4cef659a8009c5cb4f5708336ae37654d23653b3

Not possible to do a per-rev bisect?

Sorry didn't read the last comment fully, thanks for the bisect.

This is actually broken in FireFox as well. 

It appears onTouchStart they start looking for scrolling reaching a maximum threshold and then take over scrolling. They set a repeating timer checking
the scroll position on the body element:

document.body.scrollTop > this.startPosition + 40 && (window.clearInterval(this.scrollChecker),

Obviously this is not true anymore for ScrollTopLeftInterop enabled. But is easily fixable with using: document.scrollingElement

This doesn't appear to be in a library but in the game logic itself. I'll try to reach out to nytimes.

We've reached out to nytimes contacts and we have been advised they are aware of the issue and working on a fix.

BTW I want to point out that this is the sort of site compat issue that makes doing breaking changes like  issue 157855 .  Previously Firefox users were penalized here because the site was expecting non-standard behavior while Firefox was following the spec.  With our change the site will be updated and now work correctly cross-browser.  Yay!

Thanks for driving this Dave!

verified this worked fine on 2017/08/03 mini crossword on chrome canary 62.0.3175.0