I think it has to do with compile-time checking of whether the message/display will fit within the containing frame or window. So it positions the second "<indicator>" where it needs to be to fit whatever value might come before it.I could argue that this is a bug, but what’s the point as it is possibly the “expected behaviour”.