6 items
Record browser bugs with replayable steps and screenshots, then Copy CSS Selector, XPath, and DOM context for faster QA handoffs. Record browser bugs as replayable test artifacts with the selectors, steps, screenshots, and DOM context engineering needs to reproduce the issue. When an issue appears, start a Bug Replay and follow the browser path that triggers it. Samelogic preserves the interaction sequence, affected elements, page context, screenshots, and repro steps in one shareable artifact. This is intentional QA capture, not passive session replay. You choose when recording starts, reproduce the issue, review the evidence, and share only the bug context your team needs. Unlike a basic screen recorder, Bug Replay stays connected to the affected page elements. Select an element to capture its CSS selector, XPath, JS path, stability, screenshot, and DOM context. Engineering gets more than a video: what happened, where it happened, and how to reproduce it. What You Get - Record an intentionally started browser bug replay - Capture the interaction sequence and generate repro steps - Preserve affected element and DOM context with the replay - Inspect element and copy CSS selector on any page - Copy CSS selector, XPath, and JS path - See selector stability before you save - Attach element screenshots or full-page screenshots - Save locally or sync to share with your team - Export replay-based repro to Jira or Linear - Give QA, engineering, product, and support the same evidence How It Works 1. Start Bug Replay when you find an issue 2. Follow the steps that reproduce the failure 3. Select the affected element to capture selectors and DOM context 4. Review, save, and share the replayable test artifact Sign in to sync captures to your workspace and share them with your team. No long write-ups. No missing context. No extra clarification cycle. Instead of "I think it is this," send: "This is the exact element. Here are the steps. Replay what happened." Record the bug. Capture the exact element. Share replayable QA evidence.
Jul 25, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.