Screenshots
Every new comment carries a screenshot of what the reviewer saw, with the element outlined. Mark private parts of your page to keep them out, or turn screenshots off for a project.
When a reviewer clicks an element to comment on it, the toolbar takes a screenshot of the page as it looks at that moment. The comment box shows it before they send, and they can leave it out with the × next to it.
You see the screenshot under the comment in the dashboard. Your coding agent sees it too, and the REST API returns it with the comment.
What a screenshot shows
- Area: the part of the page in the browser window, at the reviewer's scroll position, rather than the whole page or the element alone
- State: the page as it was when they clicked, including text typed into fields, menus they opened by clicking, and sticky headers
- Outline: a line around the element the comment is pinned to
- Size: at most 1600 pixels on the long side. A wide desktop window is scaled down, while a phone screenshot keeps its size.
What a screenshot leaves out
The toolbar draws the page from its HTML instead of copying the screen, so these stay out:
- the comment toolbar, its pins and the comment box
- anything outside the page: the address bar, tabs and other windows
- any part of your page you mark private
Keep private parts out
Add data-annoty-mask to any element whose content must not end up in a screenshot. It shows as a solid grey box instead:
<div class="customer-card" data-annoty-mask>Jane Doe, jane@example.com</div>Password fields show as dots, as they do on screen. Mark anything else private yourself, like customer data in an admin panel reviewed through embed.
Turn screenshots off for a project
When too much of a site is private to mark, turn screenshots off for its project: open the project → Edit → clear Take screenshots → Save. It covers every feedback session in the project, through the proxy link and through embed.
From then on, the toolbar takes none. A toolbar that was already open may still show one in the comment box, but the comment is saved without it. Screenshots already taken stay with their comments; delete a comment to delete its screenshot. Through the REST API, it's the project's screenshotsEnabled field.
What may come out blank
The toolbar draws the page itself, so a few things can't be copied:
- images and fonts from another domain that doesn't allow it with Cross-Origin Resource Sharing (CORS) headers
- embedded frames, like YouTube videos, maps or payment fields
- hover effects and the browser's own dropdown lists
Through the proxy link, your own site's images load through annoty.site and show fine. If the screenshot fails, the comment is sent without one.
Embed on a site with a Content Security Policy
The toolbar loads its screenshot code from api.annoty.app and draws the page
through data: and blob: images. If your site sends a Content Security
Policy, allow https://api.annoty.app in script-src (the embed script
already needs it) and data: blob: in img-src. Without them, comments still
send, without screenshots. The embed script's other sources are under Content
Security Policy.