Olli Pettay [:smaug][bugs@pettay.fi] Reporter
	Description • 19 years ago

NS_EVENT_FLAG_NO_CONTENT_DISPATCH flag is not checked in nsDocument::HandleDOMEvent nor in nsXULElement::HandleDOMEvent.
If that is added to nsDocument, middle mouse pasting stops working in Editor.
Not sure what breaks if it is added to nsXULElement.

	Olli Pettay [:smaug][bugs@pettay.fi] Reporter
	Comment 1 • 19 years ago

Changing summary now that bug 234455 has landed.
We should try to remove mForceContentDispatch
http://lxr.mozilla.org/seamonkey/source/content/events/public/nsEventDispatcher.h#163
Or at least decide when and how NS_EVENT_FLAG_NO_CONTENT_DISPATCH should work.

	neil@parkwaycc.co.uk
	Comment 2 • 19 years ago

Is the problem that editor wants middle mouse click events but content doesn't?

	Boris Zbarsky [:bzbarsky]
	Comment 3 • 19 years ago

So as I understand it, middle-click events are wanted by chrome (at least in some cases, possibly in all?) and editor and "not wanted" by content (as in web page onclick handlers don't check which button was clicked, typically).

Which brings me to two questions:

1)  Are the chrome handlers running in the system event group?  The ones that
    listen to events in HTML documents should be, but I guess others may not be.
2)  What about the editor handlers?

As in, perhaps we should just dispatch middle-click to the system event group?  Or would that break chrome stuff in some cases?

	neil@parkwaycc.co.uk
	Comment 4 • 19 years ago

(In reply to comment #3)
>So as I understand it, middle-click events are wanted by chrome (at least in
>some cases, possibly in all?) and editor and "not wanted" by content (as in
> web page onclick handlers don't check which button was clicked, typically).
>
>Which brings me to two questions:
>
>1) Are the chrome handlers running in the system event group?  The ones that
>   listen to events in HTML documents should be, but I guess others may not be.
If you mean the click handlers in chrome XUL, then no, they just use onclick.

	Boris Zbarsky [:bzbarsky]
	Comment 5 • 19 years ago

> If you mean the click handlers in chrome XUL, then no, they just use onclick.

And they check for middle click?

I guess the question is this.  What dispatch is prevented by NS_EVENT_FLAG_NO_CONTENT_DISPATCH right now?  What dispatch _should_ be prevented?  Why do differences between the two arise?

Then we fix the things that come up in answer to the last question.  ;)

It sounds to me like the answer to the second question is:

  Dispatch to event handlers in the normal event group attached to nodes that
  are not in chrome.

or something like that?

	Masayuki Nakano [:masayuki] (he/him)(JST, +0900)
	Comment 6 • 12 years ago

I don't understand this well, but...

(In reply to Boris Zbarsky (:bz) from comment #5)
> I guess the question is this.  What dispatch is prevented by
> NS_EVENT_FLAG_NO_CONTENT_DISPATCH right now?

non-left button's click events are prevented.

> It sounds to me like the answer to the second question is:
> 
>   Dispatch to event handlers in the normal event group attached to nodes that
>   are not in chrome.

I guess that this is right approach.