Why is that? I expect because the first one passes, it can proceed with the click action.
Hi. I agree. I wish I knew what WebDriver does to “prove” something is clickable and then moves on to say it’s unable to do what it just claimed it can do.
What it’s saying in the error is, if it were to click the target, something else would receive the click because it’s in the way.
If I had to take a guess (and that’s all this is – a guess) I’d say that WebDriver, communicating with the browser, not the page, is failing to build a coherent model of the complete rendering context of the page – and if the stacking context is missing (or otherwise messed up) between the two ends of the conversation, it would lead to the kind of thing you (we) are seeing here.
By leaving WebDriver out of the conversation, I no longer run into these issues – frustration over (for me, anyway).
More on stacking context here: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Positioning/Understanding_z_index/The_stacking_context and here https://www.w3.org/TR/CSS2/zindex.html