It’s now an issue for any edit that involves a second new tab or window.
Fortunately it doesn’t actually stop anything processing correctly, but it is annoying. It’s primarily, but not exclusively, a Chrome issue. But I’m sure all other browsers will follow Google’s lead and add the same restrictions even if they haven’t yet.
I need to find a new way to code these processes, but that still works in a user-friendly way across multiple device types. It’s not an easy thing in an environment as complex as ours.