I use "wait until element is visible" keyword before every "click element" keyword. But now our web application is working slower and basically all of my tests fail. I keep getting error messages like the followings, all because the page is still loading, the navigation has not been finished, and robot does not wait:
"StaleElementReferenceException: Message: stale element reference: element is not attached to the page document (Session info: headless chrome=102.0.5005.61)"
"ElementClickInterceptedException: Message: element click intercepted: Element is not clickable at point (1385, 376). Other element would receive the click: ..."
(Unfortunately, robot documentation does not mention here that "visible" does not mean that the element really is visible and clickable....)
I can not put in sleep times before every "click element" keyword. I can not handle random loading times with explicit waits. It is such an obvious problem and I'm surprised I could not find a simple solution for it yet....
So how can I make sure that before running "click element" keyword, robot framework waits until the element is actually clickable?