Test Case for Chromium bug 837185

  1. Trigger Protocol and notice that Chrome does nothing at all because the protocol is unregistered
  2. Register an external protocol, eg chromiumtest10:// and point it at notepad.exe
  3. Trigger Protocol again (identical to step 1)
  4. Tick "Open these types of links in the associated app"
  5. Click "Open Notepad" and notice that Notepad opens
  6. Unregister the protocol
  7. Trigger Protocol again (identical to step 1)
  8. 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.