Thanks to @dcaliste and @tomin this will be fixed in the next release (after 4.4.0.58), so I’ve tagged the bug as “fixed”. If you still experience this after the next update, please flag it up.
Thanks to everyone who contributed to the thread too and made the issue clear, and to the Bug Coordination team for raising the bug.