As per a few posts back, this is a bug in Safari and therefore it's in Apple's court to resolve.
It seems we were able to reproduce a test case which proved the issue wasn't directly related to our code. I reported it to Apple but they closed it as a duplicate. If the issue still persists, you should perhaps report it to Apple directly. It will also get closed as a duplicate but at least they may realise it's having a further reaching impact.
It seems we were able to reproduce a test case which proved the issue wasn't directly related to our code. I reported it to Apple but they closed it as a duplicate. If the issue still persists, you should perhaps report it to Apple directly. It will also get closed as a duplicate but at least they may realise it's having a further reaching impact.
