This doesn't seem to be the behaviour on my machines (Linux and Windows), where mouse3 is back.