Community
Participate
Working Groups
code from HEAD Currently when an exception occurs we either trap it and eat it or we throw a general kind of exception and let the launch framework handle it. A good example of this is when you launch a remote debug session, if *anything* goes wrong we throw an IOException and let the platform launch framework handle - which surfaces as an error dialog and not-helpful message. We should improve this by specializing exceptions so that we can handle them differently when different failure cases occur. For example if the connect timed for a remote debug session, we could throw a specialized exception that could be handled differently by the JavaScriptLaunchDelegate.
