Community
Participate
Working Groups
- from the plug-in registry page, type in a bogus URL for a plugin, such as "foo/plugin.html" - nothing happens. No failure is reported. The calling code supplies an errback function to the promise. I traced the code through the pluginregistry and it seems to not be detecting the error case.
I think this is an important consumability bug, so marking RC1. I often forget the leading backslash and type "plugins/myPlugin.html" which silently fails, instead of "/plugins/myPlugin.html" which will work. We need to get the error case so the user can figure out if they typed the wrong name.
This was also causing my 404 pluginregistry test to fail. I checked in a fix for this earlier on today. You now get a nasty/hurtful red "Error: Load timeout for plugin: http://localhost:8080/plugin/hoho" message after 15s as well as in the console