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...
New options were added to the ScreenshotOne API to stop scrolling screenshots when a given selector is reached.
1 min read
Use command line interface to automate screenshots in your workflows with ScreenshotOne.
1 min read
Google Cloud gives $300 in credits for 3 months for experimenting. And I decided to give it a try, but not because of the free credits.
4 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.