Bugzilla

When one visits a URL that doesn't match up with a host (e.g. `http://example/`), the aboutNetError page will fixup the URL and suggest something different.

The URL will be fixed up to something like `https://www.example.com/` and then checked in the background to see if there is an IP corresponding to it. Because that check could find  the fixup doesn't make sense, or it could potentially take a long time, we opt not to show the help text containing the link until after we confirm the fix up makes sense.

However, this sometimes causes a flicker to occur on the page load. 

We should consider a smoother way of presenting this to the user. This will likely involve input from UX.

When one visits a URL that doesn't match up with a host (e.g. `http://example/`), the aboutNetError page will fixup the URL and suggest something different.

The URL will be fixed up to something like `https://www.example.com/` and then checked in the background to see if there is an IP corresponding to it. Because that check could find  the fixup doesn't make sense, or it could potentially take a long time, we opt not to show the help text containing the link until after we confirm the fix up makes sense.

However, this sometimes causes a flicker to occur on the page load, namely text suddenly showing up near the description.

While not ideal, I think this is a sufficient existing solution because the helper text shouldn't block the page from loading. Even so, we should consider a smoother way of presenting this to the user. This will likely involve input from UX.