Why do some events show up multiple times in the text? This is on my laptop, with one mouse: https://www.dropbox.com/s/bpdx13wkny60ot4/Screen%20Shot%202020-08-29%20at%205.12.10%20PM.png?dl=0

I still need to figure out how to make the UI more understandable. I'd like to show all events as they arrive, not just the last one… but they should not pile up. Suggestions welcome :)

I've changed the way we display the stream of events, hopefully it's easier to understand now? (Also a little more interesting visually)

Hah, I like it! The way the colors work confused me for the first 10 seconds and I wonder what it'd be like if the color-changing meant "time from expiration", so each square would softly animate through a color sequence and disappear, but it's fine as-is too. Someone's got to push the edge of interesting vis. :) also, maybe show the name of all of the event columns in gray when there aren't any events of that type? makes it a bit more informative, and also like a game (to see if you can activate them all) *event rows

I've added the event column in gray, and changed the colors—thanks for the suggestions!

🎉

@fil could this help? https://observablehq.com/@mootari/monitoring-events

thank you Fabian. I'm happy with the current version of the notebook

The link on Yuri's name is broken.

fixed, ty!

Looks like `types` & `locations` are never used.

This notebook has been super helpful for me, so thanks! I do want to suggest that elaborating exactly why you still want to call preventDefault() in the touchstart callback may be useful for some people, myself included. (I have a very strong stomach and tend not to get seasick from much, so, I'm like, 'what's the real problem here?' :) Plus I'm looking at this on desktop anyway so I can't tell by testing it out.) Is the problem that the pointermove callback will be called simultaneously for both touch and mouse events? I think people would benefit from having it stated explicitly. :) Also, the browser market is pretty ready for the PointerEvent API at this point!

Thank you! I've added a reference to the paragraph above, which mentions that without preventDefault, "a dragging gesture results in the whole page moving"—that's because the default behavior on touchstart is to scroll the page, and doing both a scroll and the drag behavior is really upsetting. > looking at this on desktop anyway You're missing most of the action ;-) (The browser market is about 95%, it seems?)