You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
I still think that those affected should work with the Apple devs via the bug tracker I opened to resolve it. They are there, they want to help, they need assistance to help. If they have a bug or regression then they want to discover it as it likely affects a lot of websites in some subtle way.
I have no idea how to do so.
Dammit
@Velocio
So we currently have:
Which does imply there's something about some users, most likely some configuration that results in Safari behaving differently for them. Perhaps it's VPN, perhaps it's a privacy setting, perhaps it's a state/cache setting.
I still think that those affected should work with the Apple devs via the bug tracker I opened to resolve it. They are there, they want to help, they need assistance to help. If they have a bug or regression then they want to discover it as it likely affects a lot of websites in some subtle way.