Media
4 items
Description
Inspect extension storage, page sessions, cookies, selectors, colors, and accessibility contrast in one developer toolkit. CIPX Toolkit is a developer utility for Cisco In-Product Experience workflows. It brings browser state inspection, page-element tooling, and accessibility checks into one persistent Chrome side panel. STORAGE EXPLORER Inspect three storage sources without digging through multiple Developer Tools screens: • Extension Storage - View everything CIPX Toolkit stores through chrome.storage.local. • Page Session Storage - Browse sessionStorage for the active page. JSON strings are parsed into expandable trees automatically. • Site Cookies - Review cookies scoped to the active site, including Domain, Path, SameSite, Secure, and HttpOnly attributes. Search keys and values, expand nested objects and arrays, edit individual extension or session entries, export a source as JSON, or clear data after a confirmation prompt. CIPX STORAGE IN DEVTOOLS Open Chrome Developer Tools and select CIPX Storage for a wider view of extension data, inspected-page session storage, and active-site cookies while debugging. CSS SELECTOR AND XPATH INSPECTOR Activate the selector inspector and hover over any element to see a uniqueness-validated CSS selector, XPath, value, computed CSS properties, and live match count. • Click to copy the CSS selector. • Shift + Click to copy XPath. • Alt + Click to pin an inspection card. • Press Escape to stop inspection. Recent selectors are retained in history so they can be copied again later. The selector engine prefers stable attributes, escapes complex identifiers, filters framework-generated classes, and supports shadow DOM and iframes. COLOR AND ACCESSIBILITY TOOLS Sample any screen pixel with the EyeDropper API and copy the result as HEX, RGB, or HSL. Build a reusable palette history and test foreground/background combinations against WCAG AA and AAA contrast requirements. PRIVACY AND SECURITY CIPX Toolkit does not send browsing or storage data to an external service. Page tooling runs only after the user invokes it. Cookie operations are restricted to the active site, and clear operations require confirmation.