As noted above, this is an issue we’re aware of. We talked about it recently internally, and it is unfortunately is a bug originating from Qt. We decided to put it off as we’re going to be upgrading Qt soon, and it makes sense to wait and see if it goes away, before putting effort into a workaround (which looked difficult to do).
This would be my preferred approach in general.