Skip to main content

​
Included by default

Opening the default dialog captures locally. The feedback endpoint receives the report only after Send. Rendering may make requests for existing page resources; this is not a guarantee that screenshot creation causes zero network activity. Cookies, local storage, console/network logs, action history, user IDs and repository contents are not automatically collected or attached. Request cookies are also omitted during upload.

​
Basic masking

In html2canvas’s cloned document, Sighting hides input, textarea, select, editable elements and [data-feedback-private] sections. The original page is not changed. The Sighting launcher and dialog are excluded from rendering.
This is not a general redaction or secret-detection engine. Other visible text, images and page paths may contain private data. Custom elements, embedded content and unusual rendering should be reviewed in your app. Use the screenshot preview and mark sensitive regions deliberately. The SDK does not currently let users paint over or blur regions themselves. If a path includes identifiers, use the headless API to transform context.url before calling send(). You control the receiving endpoint, access policy and retention period. There is no Sighting-hosted storage or built-in delete-report API in this release.

​
Rendering limits

Sighting uses html2canvas 1.4.1, which reconstructs the page from its DOM and supported styles. It does not capture the desktop, browser chrome, another tab or a native application. Unsupported CSS, cross-origin resources without appropriate CORS headers, embedded iframes, video and some canvases can render differently or be absent. It should not be described as a pixel-perfect browser screenshot. The visible viewport is captured, not the entire scrollable page. Image scale is capped at 2 and the resulting PNG must fit within 5 MiB. Upstream documentation: configuration and rendering limitations.

​
Browser and styling requirements

Use a modern browser with native dialog, Shadow DOM, dynamic import, canvas, Blob, Fetch, FormData, URL and AbortController support. No legacy-browser polyfills are bundled. ESM import is safe on the server; UI and capture need the browser. The default widget has a fixed warm dark theme, a floating bottom-right launcher and responsive dialog styling. It respects reduced motion and provides keyboard focus states. Strict Content Security Policy or Trusted Types rules can require adapting the inline markup/styles or using the headless API. Chromium was tested in the included demo. Compatibility with other engines and complex host applications has not yet been comprehensively tested. There is no native mobile SDK.