I'm not sure "network error" load events are well spec'd. For example, in gecko we treat about:neterror as cross-origin whole I believe chrome treats its network failure URL as same-origin.
So we might need some company shim code here. Maybe if the frame's load event fires we could check its window.location. If it doesn't match the original URL, then assume it's the net failure page.
Would that work?
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by bke...@mozilla.com
, Jun 7 2016