Rick Byers

Note that re-running sass as per the instructions caused a lot of updates to main.css which broke the app for me. Since this change is so trivial I just hand-edited...

Weird, now I see reload preserve game state. I definitely lost my game state on a reload earlier.

Sorry for the trouble, this is a breaking change in Chrome 56 to [improve scroll performance](https://developers.google.com/web/updates/2017/01/scrolling-intervention). You probably need to add an appropriate `touch-action` [CSS rule](https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action) to explicitly disable touch...

> though allowing the URL bar to show/hide isn't a browser bug but innate in how the web works today. I meant that the fact that the URL bar hiding...

I also filed https://code.google.com/p/chromium/issues/detail?id=163900 to track this specific scenario (it's conceivable it would be fixed, before the more general and harder problem in issue 161054 is addressed).

Whoops, didn't mean to close

This magic '100' threshold is just an implementation detail around the tradeoffs between the cost of maintaining a bunch of fine-grained rectangles and the performance benefits of the optimization. IIRC...

I've included a high-level overview of the problem [here](https://github.com/RByers/EventListenerOptions/blob/gh-pages/explainer.md), along with a partial solution we're working on.

I've made [a screen capture](https://www.youtube.com/watch?v=6-D_3yx_KVI) explaining this feature and the related passive event listener features of dev tools.

Mobile Safari exposes TouchEvent, right? Desktop Safari doesn't support touch at all, so no surprise not to have it there. Anyway further alignment on any differences between browsers SGTM. Anything...