Currently Edge only (from what I have tested). The issue already presented in FireFox in earlier versions, now also in Chrome. Not sure if it will be fixed in future versions...
