# preview_try (https://lazyfrog.dev/docs/tools/preview_try)

{/* Generated by scripts/generate-docs.ts from the gateway's registered tools. Do not edit. */}

**{"Try the page"}** · Can change or delete

<p>{"Presses the project's own preview page in a clean browser and says what happened, because a screenshot presses nothing. Use it before saying a player, menu, slideshow, form or search works. Steps run in order, up to 20: click, type (value), select (value), upload (a test file on a file field or the button that opens one: value photo.jpg, the default, photo.png, document.pdf, notes.txt or sound.wav), press (value: a key), scroll (or value top, bottom), wait (ms), expect (text or selector, state visible or hidden; or value: a field's value, a list's chosen option, \"checked\"), media (each audio and video element, whether its time is really moving, its volume, its errors; value play plays each first, as a built-in player's button would), screenshot (up to 4), measure (text or selector: where each match is in pixels, and how far apart their tops, centres and edges are; for \"it isn't lined up\"). click, type, select, upload and expect name what they act on as a visitor sees it (text) or with selector. viewport mobile (the default, with touch), tablet, desktop or wide, or width: any width in px. Each step reports whether it worked, the page it led to and sideways scrolling; a click that fails stops the run, and says when something else is on top. The result has the browser's errors and the page after the last step. Preview only: steps change the preview's data as a visitor would, never the live site. Sign-in: sign in with http_request and pass its cookie as headers (it goes into the browser's cookies, so the page's own requests have it too), or type into the form. A share, a copy and a download are reported (a share answers as if the visitor shared). It tests what a browser can do: it hears nothing, so it can't say how something sounds, and it isn't a real phone."}</p>