Thanks for your PR, @@Dona278. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

I'm comfortable on approving the PR with the suggestions that @ilonatommy did, and also @ilonatommy if you have time can you give a double test? Maybe with an old and a new chrome/edge version?
Please let me know, if you don't have time to do it I'll try.

@thaystg I'm not an expert in this area, so if you think the change is good enough, I'm happy with it.

Do you know if this affects debugging under VS or is this just for debugging directly from the dev tools?

If can help: with that change, VS debug still works, and because all stuffs are under "display browser debug information" context and are based only on what browser returns back if lanched with specific command, I think that VS debugging isn't affected.
Meanwhile I will update the code to reflect your the suggestions.

@thaystg after applied suggestions I saw that the code can be changed to a simple "if it is already correct use as is, othewise keep its query string and append to the default browser devtools path". I also added comment which explain that with example of new (both chrome and edge) and old version. @javiercn now I think it is more clear the reason why.