Focus on element feedback and keep History on the page - #28
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Element capture and History should stay beside the page being reviewed. This removes new Region/PDF capture, replaces the mode picker with a compact element workflow, adds Save & pick next and editable notes, and opens History in a private on-page panel with an extension-menu fallback on restricted pages. Previously saved Region, Visual, and Add Content records remain readable and exportable.
Embedded History requires a source-tab and editor-document-bound session; saved History remains unavailable to page content scripts. New Element records are reconstructed from allowed fields, and edits respect the storage budget.
Validation: 49 automated tests plus release assertions, release check, package verification, and diff check passed. The owner accepted Element capture and the History panel. The real Chrome for Testing toolbar opened History in the original page with one tab and the unmodified release manifest. Independent headless checks covered editing, selection, all five export actions, close/Escape, and the popup document fallback; those tests added a localhost-only host permission. A browser JSON export was imported through an MCP stdio client and used to build a brief.
The existing unpacked test profile initially retained old background behavior after a browser restart. Enabling Developer mode and explicitly reloading the extension resolved the reproduced new-tab behavior. The release checklist now requires the actual toolbar check after replacing an unpacked build.
Store submission remains separate: current screenshots/listing, the remaining acceptance checks, and upload/review readback are tracked in docs/store-release-1.8.0.md. No Store upload has occurred.