Matt Craig

At a minimum this needs a check that what is being dropped is a widget, and behave appropriately if it is not. Not sure what "appropriately" is...

@kaiayoung -- I just added up/down buttons in the notebook example.

I hadn't thought about it that way, but yes. I think the only question really is whether the size of the widget includes the border and padding (if any) or...

For reference, the coordinates currently returned are: ## Location of the mouse event These attributes are standard properties of HTML mouse events. + screenX, screenY: Coordinates of the event relative...

> Normalized would be nice Just to be clear, you mean one normalized coordinate pair, or do you mean normalized versions of each of the x,y coordinates listed above? (screen,...

> And you never know the try image size in the browser right? The only in-browser image size I really trust is the naturalWidth/naturalHeight. My understanding is that the ``...

> Thank you for anyone who takes a look into it. You rock! ;) Thanks 😀 What browser are you using on Linux? Some event behavior depends on both browser...

@LukaPitamic sorry for the delay. Any chance you could send me the output from the javascript console when this happens? To see the console, open a notebook in Chrome, then...

Thanks for the report -- I'll try to track down the issue (I do think it is an `ipyevents` issue). Also, awesome-looking tool you have developed 💯 !

I'm not quite sure what to do about this. The original motivation for this was to make sure that handlers for keyboard events didn't have to worry about colliding with...