Fix find_button to find the exact match for the button

[danni]

Including only normalising the space.

This also means we only make one XPath request.

[danni]

Was generally thinking of going through and cleaning up the XPath for all of the steps to reduce the number of round trips to Selenium required to use LWD.

[npilon]

I'm not convinced that generating complicated xpath like this is actually a win. It definitely improves performance, but I can barely read it.

[danni]

What would make it more readable?

[npilon]

Perhaps starting with '//button[normalize-space(text())="{value}"]'.format(value=value) and then using += '|stuff' to expand it? I think in this case I'd find that more readable than a generator expression and join.