Also echoing that this problem still exists on 2.0, regardless of having legacy terminal switched on or off.