Lassi Heikkinen

Yeah that would be great!

Might as well update 0.31 for Firefox 91 as per https://hg.mozilla.org/mozilla-central/file/tip/testing/geckodriver/doc/Support.md#l28

A likely culprit seems to be the [keyword itself](https://github.com/robotframework/SeleniumLibrary/blob/c6e28bdda61abefefa875f4ef8661d7e2a6f81ca/src/SeleniumLibrary/keywords/element.py#L739) which uses `ActionChains.move_to_element` instead of `ActionChains.scroll_to_element`.

Duplicate of #1767 In the meantime, you can use and extend a SeleniumLibrary plugin like [this](https://gist.github.com/Brownies/8167b6868a0801539c7d14ce484be4d9) to handle stale elements.

Probably a duplicate of #1780

Not that I know of.

Have you considered getting a free certificate from https://letsencrypt.org/ ?

I'll see if I can fix this and get the acceptance tests running on Firefox too.

Bad news, switching to `ActionChains.scroll_to_element` does not fix the problem. It's also present with RF 6 and selenium 4.7.2 with Firefox 108. Maybe this is a Selenium or Geckodriver problem?

Yeah, this is an ancient Geckodriver issue and they will not fix it until W3C updates the WebDriver spec: https://github.com/mozilla/geckodriver/issues/776#issuecomment-355086173 Might as well close this issue because the problem is...