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...
A new option has been added to fail or not to fail the screenshot rendering if there is nothing to click on.
1 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
Daily, I work as hard as I can to ensure that ScreeenshotOne is the best screenshot API out there possible. But I rarely share updates but trust me, a ton of them might go unnoticed. Let's fix this situation.
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.