Difference in behavior between opening url with Hyperlinq and browser

I have a script that helps me bunch up a group of urls (YouTube videos) and crafts a new url that would then generate a playlist out of it.

That script would generate a URL such as:

https://www.youtube.com/watch_videos?video_ids=As4tO4wqQUY,_TMZsPjoGJA

If you open it in your browser, it will redirect to a url watching the first video and a generated playlist for those videos. It will have the &list=[playlist id] in the query string.

https://www.youtube.com/watch?v=As4tO4wqQUY&list=TLGGP-4E4IDmXykyNTA5MjAyNQ

Problem is, if I put this url in a Hyperlinq which I could then open from LINQPad to my default browser, it only navigates to watching the video but no playlist appears to be generated.

new Hyperlinq("https://www.youtube.com/watch_videos?video_ids=As4tO4wqQUY,_TMZsPjoGJA").Dump();

Funnily enough, I could open it within LINQPad through Util.DisplayWebPage() and it generates fine, except I don't have direct access to the URL since we cannot manipulate the page at all.

This is probably not a problem necessarily with LINQPad but how the browser is launched or something. Opening the url from a command line works still.

Could this be looked at?

Of course, I could write the code to send the request directly and extract the redirect url, then work with that, but the behavior would probably be surprising to others who are unaware.

var handler = new HttpClientHandler();
handler.AllowAutoRedirect = false;
var client = new HttpClient(handler);
var response = await client.GetAsync("https://www.youtube.com/watch_videos?video_ids=As4tO4wqQUY,_TMZsPjoGJA");
if (response.StatusCode == System.Net.HttpStatusCode.SeeOther)
    new Hyperlinq(response.Headers.Location.ToString()).Dump();