Alas not.
This is a change implemented in 86. to patch a security risk, changing registry entries is not the way around this issue as it will just re-expose you to those risks, the marked solution should be unmarked as it will lead to a compromised system.
The change is documented here 036150cfca14e4f91b7f06855b19462575aed37f - chromium/src - Git at Google and was a correction of an attempted earlier fix.
I’ve done a quick check all the way back to 2016r4.1 and they all now fail when running a web project. This is the way things will be going forward and it’s an issue that Xojo needs to now address. I’m not sure how you’re going to address the legacy issues with this one.
The issue is as follows:
Xojo has been surrounding its shell open url with quotes e.g.
"http://127.0.0.1:8080/"
this is then passed to Computer\HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command on a shell open request which used to be:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- "%1"
so the file being run with command line params was:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- ""http://127.0.0.1:8080/""
note the double quotes, this just happened to not matter and everything worked ok.
The error here was that the quotes are not required around the url as they will be quoted anyway when the %1 is replaced with the url.
The problem now occurs because you’re adding quotes which are no longer required and probably shouldn’t have been added in the first place (unable to confirm with 100% certainty as I don’t know when or if %1 was ever changed to “%1”, I’ve checked a really old VM and its quoted there so who knows, maybe it wasn’t in the dark ages, but I digress).
So now you’re sending a quoted url to a system that isn’t expecting quotes and its instantly encoding those to ensure that nothing nefarious is taking place which causes the whole problem.
You can test this by throwing the following into a command line and watching the reproduction of the problem:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --single-argument "http://127.0.0.1:8080/a b/"
where as the following works:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --single-argument http://127.0.0.1:8080/a b/
I’ll let someone else put the ticket in as I’m no longer reporting bugs.
Also, someone at Xojo might want to raise a ticket with chromium mentioning that previously (erroneously?) quoted urls are failing after the change which could stealth break a load of legacy apps so they might want to check that out.