If possible I would like to know if the unreleased 5.1 actually fixed this issue or not, did you test it or have any information on this?
Just to know if it’s worth waiting for full 5.1 release (5.1 Preview 2 currently available to download, so it shouldn’ take that long hopefully).
So we don’t have to implement this workaround, where as JEFFREY_EPSTEIN mentioned above, this workaround causes some side effects (if true).
Thank you!