PostHog / PostHog/posthog

Skip Inactivity Only Measure Cursor Movement Not Keyboard Usage

Open
#36,862 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature/replay
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Bug Description

Skipping inactivity only seems to factor in cursor movement not keyboard movement. A user wrote in that makes games and at least one of them can be primarily used with just a keyboard. I was able to replicate it and for ~5-10 minutes of playing with just the keyboard it skips inactivity that is actually activity and resumes for a short bit after moving the mouse in the middle of the play time.

How to reproduce

Probably easily reproducible (haven't confirmed) on any page with session replay

  1. Use up/down/left/right keys for a couple minutes on any page where session replay is enabled
  2. Move mouse at the beginning for 10 seconds, then sometime in the middle, then at the end
  3. Watch the session replay with skip inactivity enabled

Additional context

The easy answer is turn off skip inactivity but this seems like a worthwhile improvement to make if we can, I've run into a few companies using PostHog with games lately so I have to imagine there's some value there.

Debug info
- [x] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the session replay behavior controlled by the “skip inactivity” option and reproduce the issue using only the arrow keys, with mouse movement at the beginning, middle, and end. Done means keyboard activity is treated as activity so replay does not skip those periods; no specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.