That is correct, but we are still using the “old” code in the Woo elements and there it is exactly the same behavior, so it is not a bug.
There are (at least) two improvement threads, which we will look at in due course: