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.

1 min read

Written by

Dmytro Krasun

Published on

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.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Better code examples in the playground

Better code examples in the playground

Improved code examples in the playground and added all official supported ScreenshotOne SDKs.

Read more

1 min read

Better error coverage and documentation

Better error coverage and documentation

Since a few months ago, it has been possible to check errors in the dashboard request log and get explanations and more details in the documentation. But!

Read more

1 min read

Improved errors

Improved errors

Now, errors will have relevant documentation links. It will be also possible to see why some requests failed in the dashboard and get recommendations on how to address the issue.

Read more

1 min read

Automate website screenshots

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.