Please see the announcement I attached to my other reply. I apologize for posting it a little late after sending, but that property already deals with that issue automatically, as those other workarounds were made before this property was introduced.
But in short, this is what is important: