You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into some slightly odd behavior and wanted to make an issue to make sure it was the desired behavior. When running a browser plugin programmatically where the active node is set to a node that has not been loaded by the client, I get an error (Cannot call getOwnRegistry of undefined):
If this is the expected behavior, it should at least give a better error message in pluginmanager.js
The text was updated successfully, but these errors were encountered:
I believe this is intended, but you are right in that it should throw a better error telling that you need to have your node ready to call a plugin on it.
I ran into some slightly odd behavior and wanted to make an issue to make sure it was the desired behavior. When running a browser plugin programmatically where the active node is set to a node that has not been loaded by the client, I get an error (
Cannot call getOwnRegistry of undefined
):If this is the expected behavior, it should at least give a better error message in pluginmanager.js
The text was updated successfully, but these errors were encountered: