Use the new hover option to interact with elements before rendering, and choose whether to fail if the hover selector is not found.
ScreenshotOne API now has a hover option which allows you to hover over a specific element on a page before taking a screenshot.
You don’t pay for failed and cached screenshots with ScreenshotOne.
By default, the request fails when the selector is not found. If you want to continue rendering anyway, set error_on_hover_selector_not_found=false.
If you have any questions or feedback, please let us know at support@screenshotone.com.
New features, bug fixes, and optimizations...
Before the change, there was a subset of cases when the rendering requests were failing when using the scroll_into_view option. Now, it is improved and will make rendering more stable.
1 min read
We fixed a validation issue in the ScreenshotOne playground caused by selector scroll into view.
1 min read
New options were added to the ScreenshotOne API to stop scrolling screenshots when a given selector is reached.
1 min read
Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.