Collect consecutive keypresses on input elems as "input" breadcrumb

[benvinegar]

• Only considers keypresses on INPUT or TEXTAREA elements
• Keypresses are debounced 1000ms; but a click or error will flush any queued capture
• The first keypress in a series is recorded as the start of an "input" event; only > 1000ms without a typing event will cause it to reset

[benvinegar]

Discussion: should we flush if any breadcrumb occurs in between keypresses? e.g. navigation change or XHR. For navigation change, I think we should. My concern w/ flushing on XHRs is lookahead search boxes – where an XHR could trigger in between keypresses, making for a really messy timeline.

Another idea: I switch the debounce so that the first keypress creates the breadcrumb, any we don't create a second one until the debounce clears. That should prevent shit from being out of order, and will simplify code because then I don't have to write manual flushes all over the place.

[benvinegar]

Another idea: I switch the debounce so that the first keypress creates the breadcrumb, any we don't create a second one until the debounce clears. That should prevent shit from being out of order, and will simplify code because then I don't have to write manual flushes all over the place.

Yeah I don't know why I didn't do that to begin with facepalm

Changing.