Control Deck

Description

Pick controls from a webpage and build a compact floating remote for the actions you use most. Control Deck lets you build a small, site-specific remote control from controls that already exist on the webpage you are using. Open Control Deck on a page, choose Pick Control, then select a supported element on that page. The selected element is represented inside the floating deck. The deck does not replace the website or invent new actions: it remains connected to the original page control. Supported module types in version 1.0.0: • buttons; • text fields and text areas; • checkboxes, switches, and radio-style toggles; • select menus; • range sliders; • links; • read-only live values taken from visible page text. For interactive modules, changes made in Control Deck are sent to the matching page element using normal page interactions or native form value updates and corresponding input/change events. When the page changes a supported field, Control Deck refreshes its displayed state. Read-only live values are refreshed from the original page element. Control Deck stores a separate deck for each website origin. A saved module contains a local description of the element, including selector candidates and a structural fingerprint used to find that element again on later visits. If the page changes enough that the element can no longer be identified with sufficient confidence, the module is shown as disconnected rather than silently attaching to a weak candidate. The user can then reconnect it by selecting the intended element again. The floating deck can be moved, collapsed, hidden, reordered, and restored. Version 1.0.0 limits a deck to 24 modules so that accidental captures cannot create an unbounded interface. Control Deck does not include macros, scheduled actions, background scraping, cloud synchronization, remote code, advertising, or analytics. It does not send captured page information to a server. Site deck data is stored locally through Chrome extension storage. Control Deck is intentionally activated by the user. It does not request broad host access to every website. The extension uses Chrome's activeTab permission so page access is granted for the current tab after the user invokes the extension.

Details & SEO