I am happy you have a workaround that does the job right now.
But I agree, it is not ideal.
I’ve tested the sample you provided and came to the same conclusion, by the way.
I just constructed a fix for this for the framework, which should become part of release 4.5.2.
If you’re interested, you can find the pull request here.