I know for sure I had this case very recently, where the "element not
interactable" error occured, and the element was outside the viewport,
and it also didn't scroll automatically to that element.
I remember this clearly, because I could not figure out the problem,
until I actually found an answer on stackoverflow (not the first answer
to that question, though), that suggested to watch out for scrolling.
It was only because of this that I realised that the element was in fact
outside the viewport, and explicit scrolling made the problem go away.
The application that I am testing is very old, close to 20 year, and
there are many problems with the UI, like buttons and UI elements
visibly changing after the page has loaded, so it could definitely be
some weird edge case.
I definitely agree to Marcin, that this is by no means a common
occurrence, and most of the time, the element is in fact not
interactable, i.e. disabled, when this error comes.
> [1].
>
> --
> You received this message because you are subscribed to the Google
> Groups "Geb User Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to
geb-user+u...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/geb-user/CA%2B52dQR4LgiqYiw3JY_4Civ4k%3DqfLVM9agCjZwcnwj88bk6N9w%40mail.gmail.com
> [2].
>
>
> Links:
> ------
> [1]
>
https://groups.google.com/d/msgid/geb-user/08ae974a-ecc5-440a-b246-10e2703f4e70n%40googlegroups.com?utm_medium=email&utm_source=footer
> [2]
>
https://groups.google.com/d/msgid/geb-user/CA%2B52dQR4LgiqYiw3JY_4Civ4k%3DqfLVM9agCjZwcnwj88bk6N9w%40mail.gmail.com?utm_medium=email&utm_source=footer