Dev Feedback Capture is a Chromium extension for collecting structured UI feedback from live pages, PDFs, and other browser-visible surfaces. It supports two capture modes:
Elementmode injects a lightweight in-page UI so you can click DOM elements and save selectors, styles, and notes.Regionmode captures the visible viewport, opens a screenshot editor, and lets you draw a crop around any area, including browser-rendered PDFs.
All feedback stays local in extension storage and can be re-exported later as JSON, Markdown, or an AI-oriented prompt.
- Element capture with selector, text, styles, and note metadata
- Region capture with cropped screenshot, viewport rectangle, and note metadata
- Works on arbitrary sites through explicit user-triggered activation
- PDF-friendly screenshot workflow for local and hosted PDFs
- Local history with re-export support
- JSON, Markdown, and AI prompt clipboard exports
- Draggable in-page history panel for injected pages
- Clone or download this repository.
- Open
chrome://extensions/oredge://extensions/. - Enable Developer Mode.
- Click
Load unpackedand select thewebDevFeedbackExtfolder. - Optional for local PDFs: enable
Allow access to file URLson the extension details page.
- Open the extension popup on any
http,https, orfilepage you want to inspect. - Leave the mode switch on
Element. - Click
Start Element Modeor useCtrl+Shift+F. - Hover and click a page element.
- Add your note in the modal and save it.
- Open the target page or PDF in the browser.
- Open the extension popup and switch to
Region. - Click
Capture Region. - In the editor tab, drag a box over the screenshot.
- Add your note and save it.
The cropped image, viewport rectangle, and source context are saved into the same page history as element captures.
Stored feedback items use a discriminated shape:
type: "element"items include selector, element info, and position.type: "region"items include viewport rectangle, screenshot crop, source kind, and tab context.
Older element-only captures are still loaded and normalized automatically.
Copy JSONincludes the full saved payload, including region image data URLs.Copy Markdowncreates a readable review document for issues or docs.Copy AI Promptcreates numbered instructions that refer to the saved crops in extension history.
The extension requests:
storagefor local historyactiveTabfor user-invoked access to the current tabscriptingto inject the in-page element capture UI only when requested
The extension no longer relies on static host permissions or always-on content scripts.
- Hosted PDFs should work through Region mode because the capture flow is screenshot-based.
- Local
file://PDFs may require enablingAllow access to file URLs. - Region mode captures only the visible viewport in v1, not off-screen PDF pages.
manifest.json: Manifest V3 configurationbackground.js: runtime injection and region-capture session orchestrationcontent.js: in-page panel, element capture, exports, and history renderingcapture.html/capture.js: screenshot region selection editorpopup.html/popup.js: mode switch and current-tab actionsshared.js: shared helpers, normalization, and export formattingstyles.css: injected in-page UI styles
npm testnpm run check
Build commands beyond these release/helper checks are not defined in the repo.
- Element mode depends on DOM/script injection and is not intended for browser-internal surfaces.
- Region mode stores text exports and crop data in local storage; very large capture histories will increase storage usage.
- Region mode captures the current viewport only, not full-page stitched screenshots.
- Cross-origin iframe DOM capture remains limited by browser security rules.
- Export region crops as files instead of only embedding them in JSON
- Add full-page or multi-step PDF region capture
- Add import/export for saved histories
- Add optional provider-specific AI handoff after the provider/auth shape is defined