Capturing a report
Once you’re connected, filing a report is a short loop: point at what’s wrong, say a sentence, send. uMarker attaches the technical context for you, so you never describe your browser, copy a URL, or open the console. Start to finish, a report takes well under a minute.
Open the tool
Section titled “Open the tool”On any site you’re authorized for, you have two ways to start:
Click the feedback launcher in the corner of the page (bottom-right by default, though your team can move it, or dock it as a tab on either side). Quickest when you’re already looking at the problem.
Click the uMarker icon in your toolbar, then Send feedback on this tab. It opens the same in-page tool, so it helps when the launcher is hidden behind something. If the tab was already open when you installed the extension or entered your connect code, reload it first: the tool loads with the page.
The tool takes over the page: a lens frame draws around the viewport, a badge at the top names the mode you’re in, and a small glass toolbar appears with your tools. Nothing leaves your browser until you submit. Pictures are taken as you go: each time you save a note, the tool photographs the screen you are looking at — it blinks out of the way for that instant, and the page never scrolls — so the report shows what you saw when you marked it, and Review shows you the result before you decide to send.
Point at what’s wrong
Section titled “Point at what’s wrong”-
Hover. With Inspect (the default), the deepest element under your cursor lights up with its box model drawn around it: content, padding, and the margins in orange. Everything else dims, so you can see exactly what you’re about to flag.
-
Adjust the level if you need to. Pressing
↑selects the parent element,↓goes back down,←and→move between siblings. The on-screen⌃⌄buttons do the same. It stays where you put it, with no surprise jumping up the tree. -
Click it. A note box opens right there. Type what’s wrong and press
Enter, and a numbered pin drops: one comment, attached to that exact element. Leave the note empty and nothing is recorded. -
Comment on the space, not the box. The orange margin bands are clickable in their own right: click one and your comment is about the spacing on that side, which is usually what a layout complaint is really about.
-
Repeat. Numbered pins, in order, each with its own note. Click any pin to reopen its note and edit or delete it, and drag an element or spacing pin onto another element to re-anchor it there — a dragged spacing pin becomes a comment on that element.
-
Review and send. Press Review. A drawer opens with the screenshot — every screen you marked, one under the other — and a map of every comment you wrote: tap a pin to read that note, edit it, delete it, or scroll the page to it. Then press Submit for review.
The tool then closes and sends that screenshot. You get a full-page Report sent confirmation showing how many comments went with it, and it closes on its own.
The tools
Section titled “The tools”Your project decides which tools appear and in what order, and the first one is what’s selected when the tool opens, so you may see a subset. Inspect and Pointer are always there, though: if the project leaves them out, they are added at the end.
| Tool | What it does |
|---|---|
| Inspect | Highlights the deepest element under the cursor with its box model. Click to pin that element; click an orange margin band to comment on the spacing instead. This is the one that makes a report precise: it records the element’s own CSS selector. |
| Comment | Drops a numbered pin anywhere on the page and opens its note. Use it when the problem isn’t one element: “this whole section is confusing”. |
| Highlight | Frames a region. |
| Pen | Freehand, for circling or underlining. |
| Pointer | Browse mode. Click through the page normally (open a menu, go to the next step) without leaving the tool. Use it to reach the state you want to report on, then switch back. |
Alongside the tools: a color palette for your marks, Undo and Redo (Ctrl/⌘ + Z, add
Shift to redo), Clear to remove every comment, and Exit. Press Esc to back out: from a
note first, then from the tool, and it asks before discarding work.
What happens when you send
Section titled “What happens when you send”uMarker bundles your pins and their notes with the screenshot, the page URL and your browser details — plus, when the project is set to Technical mode, the console, errors, network requests, page-speed figures and recent clicks — and files it against the project this site belongs to: the extension asked uMarker which project that is when the page loaded, so you never pick one. It’s in the team’s inbox the moment it’s filed, with all the captured context attached, because there’s no processing queue and no batch to wait for. An inbox already open on a teammate’s screen shows it on their next load.
You’ll see one of two results:
- Report sent. The confirmation appears and the tool closes. You’re done.
- A failure message that says what actually happened: a network problem, an authorization problem, or a server problem, named separately, because they need different responses from you. The launcher comes back and your report is parked on it: pressing the button retries this report rather than starting a new capture. Nothing you wrote is thrown away, and retrying can’t create a duplicate.