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.
Improved the behavior and stability of the "scroll_into_view" option
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.
Interviews, tips, guides, industry best practices, and news.
A new version of the ScreenshotOne API has been just deployed. It allows you to include the shadow DOM contents when requesting the page content.
Use a new option to fail ScreenshotOne API requests on purpose.
Starting from today ScreenshotOne can return both a website screenshot and the content in one simple API request.
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.