Maybe this only happens when you are indeed in a bad connections, but I’m note sure this is a valid case to override the default browser behavior.
True, the PR asking to implement it was the first I’ve heard someone complain. I was able to reproduce it on a slow connection, but I removed it for now, might not be that big of an issue in practice.