wait_for_selector follows your timeout

The wait_for_selector option now waits for as long as your request's timeout allows, loads the page once, and returns a clear error if the element doesn't appear.

Changelog1 min read

Written by

Dmytro Krasun

Published on

The wait_for_selector option used to wait for 30 seconds and then load the page a second time, whatever timeout you set. Now:

  • It follows timeout. The API waits for the element until shortly before the request’s timeout. If you don’t set timeout, it waits up to 60 seconds, for asynchronous requests too.
  • One page load. The API doesn’t load the page a second time after that wait.
  • A clear error. If the element doesn’t appear, the timeout_error message says so, with the number of seconds it waited.

An element that needed the second page load to appear won’t be found anymore. If that’s your case, check the selector or wait for an element that the first load adds.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
More algorithms for screenshots by selectors

More algorithms for screenshots by selectors

We added more algorithms for screenshots by selectors.

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

Fail if there is nothing to click on

Fail if there is nothing to click on

A new option has been added to fail or not to fail the screenshot rendering if there is nothing to click on.

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.