We can't really expect the user to behave in any way at all - this is a bug, and it's not expected to be quite so long term that we document it in the user guide :-)

I pointed out the simple corrective procedure of pressing and releasing the button a second time for the convenience of anyone who experiences the problem. The real solution is to fix the bug, and we're hoping very much that the developers did just that earlier today.

Rob