since I upgraded to goJS 1.6.1 document level mouse events don’t work if they happen over the GoJS surface… is this a new thing?.. can it be turned off?.. my guess is goJS marks those events as handled or something… :-S
I have 2 scenarios that suffer from this… one is a context menu that doesn’t hide when you click on goJS surface… and one is dragging and dropping from a “toolbox” that just stops when entering the goJS surface…
both those scenarios used to work fine in 1.5.5… and that upgrade is the only big thing that we changed… as far as I know.
For 1.6 we made some internal changes to event bubbling. Generally, if GoJS uses an event for something, it won’t let that event bubble up to the rest of the page. You can sometimes stop this (or explicitly do it) by setting the e.handled property of InputEvent.
Could you get 1.6.5 (the latest), which has a modification to doMouseMove (but not doMouseDown) and tell me if it fixes your problem, without adding any work-around code? In other words, remember to remove your work-around override functions.
It’s somewhat circumstantial. For instance, with that addition, perhaps panning the diagram will also pan the page.
It may be safer to do that only for certain tools, or only when no tool is running, etc. This might be safer, but I haven’t given it a huge amount of thought:
diagram.toolManager.doMouseDown = function () {
go.ToolManager.prototype.doMouseDown.call(this);
// only bubble if no specific tool is currently in use
// (toolManager is the default tool)
if (diagram.currentTool === diagram.toolManager) diagram.lastInput.bubbles = true;
};