Test Case for Chromium bug 837185
- Trigger Protocol and notice that Chrome does nothing at all because the protocol is unregistered
-
Register an external protocol, eg chromiumtest10:// and point it at notepad.exe
-
Either, download and run pre-prepared register.reg file to create the protocol,
-
or follow instructions at docs.microsoft.com to create it manually by editing the registry
- Trigger Protocol again (identical to step 1)
- Tick "Open these types of links in the associated app"
- Click "Open Notepad" and notice that Notepad opens
-
Unregister the protocol
-
Download and run pre-prepared unregister.reg file,
-
or delete the registry keys you manually created following the Microsoft guide
-
Trigger Protocol again (identical to step 1)
-
Notice that a Windows "You'll need a new app to open this" dialog appears, which is inconsistent with the results of step 1 where the protocol was unregistered:
Note that after following these steps, if you want to run them again you will need to clear your Chromium preferences to have it forget about the handler's BLOCK/DONT_BLOCK setting.