core(navigation): improve url presentation in redirect warning message

[connorjclark]

before

"The page may not be loading as expected because your test URL (chromestatus.com/features) was redirected to chromestatus.com/features. Try testing the second URL directly."

after

"The page may not be loading as expected because your test URL ( chromestatus.com/features ) was redirected to ( chromestatus.com/features )—try testing the second URL directly."

Padding the url with spaces on either side improves url detection. for example, see how the url is wrong for the old format here:

Closes #15536

[brendankenny]

Maybe need to work this more? The spaces look pretty janky and this warning is quite prominent in the report (and honestly URL detection in someone's terminal setup seems low priority :P)

[brendankenny]

Embracing the em-dash? That wouldn't solve the period though. nbsp, but that likely wouldn't survive the translation process (though extra spaces probably won't either)

[adamraine]

Honestly I would prefer a larger overhaul to the warning message. It get's pretty hard to read for long URLs:

I think it would be better to turn these into links using the markdown renderer like:

The page may not have loaded correctly because the [requested URL](https://google.com) was different from the [final URL](https://www.google.com)

[paulirish]

Honestly I would prefer a larger overhaul to the warning message. It get's pretty hard to read for long URLs:

we can use Util.getURLDisplayName plus a title attribute with the full thing

[connorjclark]

maybe:

The page may not be loaded bc...... :
- https://www.example.com
- https://www.example.com?addasdsad 

@exterkamp did this in PSI...

[connorjclark]

we can use Util.getURLDisplayName plus a title attribute with the full thing

Using Util.getURLDisplayName(url, {preserveHost: true, preserveQuery: true}) shortens it, but visually the result of that function is likely to be equivalent for both urls involved in the redirect. For example, the common http -> https case would always look the same:

for http://www.paulirish.com/ -> https://www.paulirish.com/

paulirish.com/
paulirish.com/

maybe:

The page may not be loaded bc...... :
- https://www.example.com
- https://www.example.com?addasdsad 

We'd have to support a list - in our markdown (or - simpler - encode something that means <br>. Not sure if raw \n or <br> could be considered standard-enough markdown for this to be reasonable approach), but doable: