fix: use sliding window to capture rage clicks

[daniel-graham-amplitude]

Summary

Use a sliding window for rage click instead of a buffer.

Previously, it used a buffer, which has an edge case where 3 events could happen in one window and then another 3 events could happen in the next window, and it could miss a rage click if the buffer time elapsed between the calls.

This PR fixes it so that it just adds clicks to a sliding window, where the clicks expire after a certain time, and the window gets cleared if the next clicked element is not the same as the previously clicked on element.

Checklist

• Does your PR title have the correct title format?
• Does your PR have a breaking change?: Yes

[Copilot]

Pull Request Overview

This PR refactors rage click detection to use a sliding time window, updates related tests to the default threshold, and adds configuration for rageClicks in the test server example.

• Switches from bufferTime to a manual sliding-window algorithm in track-rage-click.ts
• Updates tests to remove the overridden config and adjust expected click counts
• Changes the test-server example to accept a cssSelectorAllowlist object for rageClicks

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
test-server/autocapture/element-interactions.html	Replaced rageClicks: true with an object allowing CSS selector configuration for inputs
packages/plugin-autocapture-browser/test/autocapture-plugin/track-rage-click.test.ts	Removed test-only config override and adjusted loop counts and expected click counts
packages/plugin-autocapture-browser/src/autocapture/track-rage-click.ts	Removed bufferTime logic, added manual sliding-window management, dropped test override function

Comments suppressed due to low confidence (1)

packages/plugin-autocapture-browser/src/autocapture/track-rage-click.ts:50

• The function shouldTrackRageClick is referenced but not imported, leading to a runtime error. Either import it from the correct module (e.g., ../helpers) or replace it with the intended predicate (such as shouldTrackEvent).

        return shouldTrackRageClick('click', click.closestTrackedAncestor);

[promptless]

✅ No documentation updates required.

[tkainrad]

lgtm!

[daniel-graham-amplitude]

bugbot run

[cursor]

✅ BugBot reviewed your changes and found no bugs!

---

Comment bugbot run to trigger another review on this PR
Was this report helpful? Give feedback by reacting with 👍 or 👎

[Dogfalo]

Logic makes sense to me. Do we have a test case that covers this new scenario?

[daniel-graham-amplitude]

Test added thanks!