-
Notifications
You must be signed in to change notification settings - Fork 0
Annotate interactive / JS-revealed content #4
Copy link
Copy link
Open
Labels
area:overlayThe in-page annotation overlay (assets/overlay).The in-page annotation overlay (assets/overlay).enhancementNew feature or requestNew feature or requestideaExploratory possibility — captured, not committed. May or may not be built.Exploratory possibility — captured, not committed. May or may not be built.
Description
Activity
Metadata
Metadata
Assignees
Labels
area:overlayThe in-page annotation overlay (assets/overlay).The in-page annotation overlay (assets/overlay).enhancementNew feature or requestNew feature or requestideaExploratory possibility — captured, not committed. May or may not be built.Exploratory possibility — captured, not committed. May or may not be built.
Today the overlay intercepts every page click to select an element (
dom/selection.js), so content that only appears after a JS-driven interaction (opening a menu, expanding an accordion, switching a tab) can't be reached or annotated.Idea: allow the reviewer to trigger the page's own actions and then annotate elements that appear as a result — e.g. a modifier-click or an explicit "interact" mode that lets events through, rather than intercepting them.
Tension to resolve: this conflicts with the current always-intercept selection model (
SEL-*,NFR-4). Needs a clear UX for switching between "annotate" and "interact".