Browser Actionability Debugger
Diagnoses and resolves browser automation failures where UI elements appear visible but cannot be clicked, hovered, or focused.
A specialized debugging skill for browser automation and end-to-end testing frameworks like Playwright, Chrome DevTools, and Puppeteer. It helps developers and QA engineers identify why seemingly visible DOM elements fail hit-testing checks due to invisible overlays, stacking context issues, CSS pointer-events, active transitions, or splash screen lifecycle gates. By analyzing hit-testing diagnostics via elementFromPoint(), computed ancestor styles, and bounding boxes, it guides users to sustainable fixes at the proper UI or test layer without resorting to flakiness-hiding anti-patterns like force-clicking.
Key Features
01Inspects computed styles including opacity, pointer-events, and bounding boxes
02Provides cross-platform clipboard normalization for reliable multi-line assertions
03Eliminates reliance on force-clicking anti-patterns that hide genuine UX bugs
04Differentiates visual DOM visibility from true browser pointer actionability
0518 GitHub stars
06Detects intercepting overlays, splash screens, and z-index stacking conflicts
Use Cases
01Fixing flaky Playwright or Cypress click actions intercepted by backdrop overlays or loading screens
02Debugging interactive UI components blocked by decorative canvas layers or pointer-events: none
03Verifying multi-line clipboard copy and paste assertions across Windows and Unix environments