I take it back. Trying it again, the behaviour has reverted (i.e. the bug has come back). Not sure why it seemed to work properly once with 3.68.1, but perhaps that’s all part of the original bug, i.e. it works once but then goes wrong?
1 Like