1.382.0
Minor Changes
-
#3749
9877710Thanks @pauldambra! - Stop classifying intentional repeated clicks as rageclicks. From the2026-05-30config defaults, rageclick detection now ignores:- text-editing surfaces (
textarea, text-likeinputs, andcontenteditableelements), where rapid clicks are double/triple-click text selection rather than rage (rageclick.ignore_text_selection) +/-stepper buttons, added to the defaultcontent_ignorelist
Symbol-only keywords in
content_ignorelist(e.g.+,-,>,<) now match the element's text exactly instead of as a substring, so labels likesign-up,5 > 3, orC++are no longer treated as repeatedly-clicked controls. The heatmaps rageclick marker now applies the same suppression as the$rageclickevent.A partial
rageclickconfig object is now merged with the date-gated defaults instead of replacing them, so e.g.rageclick: { threshold_px: 50 }keeps the defaultcontent_ignorelist/ignore_text_selection. Pass an explicit value (e.g.content_ignorelist: false) to override a specific default, or a boolean to opt out entirely.Behaviour change for existing
content_ignorelist: trueusers (available since2025-11-30): the default list already includes>and<. After this release, buttons whose text contains>or<but is not exactly that symbol (e.g.Learn more >,< Back,home > settings) will no longer be suppressed. Bare>and<buttons remain suppressed. This is the intended fix, but if you rely on the old substring behaviour for those keywords, replacecontent_ignorelist: truewith an explicit array listing the exact terms you want to suppress. (2026-06-06) - text-editing surfaces (
Patch Changes
- Updated dependencies []:
- @posthog/types@1.382.0
- @posthog/core@1.30.10