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.
To be precise, for example, you were specifying a selector of some elements that is not loaded till you see it in the viewport. That behavior triggered timeout errors in the old implementation.
Now, the algorithm is improved to scroll and to try to trigger a lazy load of the specified element.
That way it is more stable and the request has a higher chance for success.
Enjoy! And if you have any questions, please don’t hesitate to reach out at support@screenshotone.com.
New features, bug fixes, and optimizations...
From today ScreenshotOne supports GPU rendering for both regular and animated website screenshots. The API now leverages the latest in graphics processing technology to bring your screenshot needs to a whole new level.
2 min read
It is a long-term move and rebuilding the ScreenshotOne dashboard was a decision to continue improving customer experience. The previous version of the dashboard was outdated and didn't serve new arising customer needs well.
1 min read
ScreenshotOne supports PDF rendering for a long time but it was used till recently by a small group of customers. Growing demand in PDF rendering required updating the API. And today, we introduce new options for PDF customization.
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.