Hi, We did have a look at this based on an open support request, but we were not able to reproduce with Chrome build 72.0.3636.109. The scenario you describe does only reproduce with build 72.0.3636.96 which is not the latest. When we know more, we will post information in that other forum posting. Thanks.
↧