Description Mark Macdonald 2013-11-14 22:20:55 EST

1. Create a plugin that implements an "orion.edit.model" service and listens to mouse or drag events, eg:

> pluginProvider.registerService("orion.edit.model", {
>     onMouseDown: function(event) {
>         console.log(event);
>     }
> }, {
>     types: ["MouseDown"],
>     contentTypes: ["application/javascript"]
> });

2. Install the plugin, open a .js file and move/click the mouse.
3. You'll see that the event object received by the plugin has only a single field:
> {   preventDefault: function() {..}   }

All of the interesting data (x, y, clickCount, etc) has been stripped out.

This is probably because the serviceRegistry interprets the event object as an ObjectReference due to the presence of the function 'preventDefault' (and possibly other functions in the 'event' field too, which provides the native browser MouseEvent).

The wiring code in dispatcher.js needs to sanitize these events, by removing function-typed fields, before sending them to the plugin.