On 03/04/2013 08:20 PM, Boris Zbarsky wrote:
On 3/4/13 1:08 PM, Zack Weinberg wrote:
It only needs to be certain of seeing the event despite anything content
can do,
In that case, a capturing handler on the chrome event listener will work fine.
-Boris
or capturing or bubbling event
On 2013-03-03 10:25 PM, Boris Zbarsky wrote:
On 3/3/13 10:12 PM, Zack Weinberg wrote:
If an event is dispatched from C++ using
nsContentUtils::DispatchTrustedEvent with both the 'bubbles' and
'cancelable' flags set false, what precisely is the difference between
targeting it at a document's
On 3/4/13 9:10 AM, Zack Weinberg wrote:
So I guess the next question is where does one put a capturing event
handler so that it will see *all* events of the relevant type regardless
of which window it was dispatched to or the contents of that window
I don't think such a thing is possible in a
On 2013-03-04 9:53 AM, Boris Zbarsky wrote:
On 3/4/13 9:10 AM, Zack Weinberg wrote:
So I guess the next question is where does one put a capturing event
handler so that it will see *all* events of the relevant type regardless
of which window it was dispatched to or the contents of that window
On 3/4/13 1:08 PM, Zack Weinberg wrote:
It only needs to be certain of seeing the event despite anything content
can do,
In that case, a capturing handler on the chrome event listener will work
fine.
-Boris
___
dev-platform mailing list
If an event is dispatched from C++ using
nsContentUtils::DispatchTrustedEvent with both the 'bubbles' and
'cancelable' flags set false, what precisely is the difference between
targeting it at a document's window and targeting it at the document's
window's chrome event handler? In particular,
On 3/3/13 10:12 PM, Zack Weinberg wrote:
If an event is dispatched from C++ using
nsContentUtils::DispatchTrustedEvent with both the 'bubbles' and
'cancelable' flags set false, what precisely is the difference between
targeting it at a document's window and targeting it at the document's
7 matches
Mail list logo