On Sat, 03 Jul 2010 00:09:53 +0200, Chris Wilson
wrote:
Can you point me to where?
Sorry, I thought you meant cancelable. The reason it does mention bubbling
and cancelable explicitly but not capturing is because each event can
always be captured, but not all of them bubble or can be canc
Jonas Sicking; Chris Wilson
Cc: Boris Zbarsky; Brett Zamir; www-...@w3.org; public-webapps@w3.org; Travis
Leithead; Adrian Bateman
Subject: Re: Custom DOM events and privileged browser add-ons; Was:
Bubbling/Capturing for XHR + other non-DOM objects
On Fri, 02 Jul 2010 18:21:31 +0200, Chris Wi
On Fri, Jul 2, 2010 at 3:03 AM, Bjoern Hoehrmann wrote:
> * Jonas Sicking wrote:
>>On Fri, Jul 2, 2010 at 1:29 AM, Anne van Kesteren wrote:
>>> On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky wrote:
I think Anne answered the question, in any case: the XHR event target
chain only cont
On Fri, 02 Jul 2010 18:21:31 +0200, Chris Wilson
wrote:
BTW, the XHR spec does not say anything about capture, iirc, just
bubbling - leaving it somewhat ambiguous.
It is actually quite explicit as far as I can tell.
--
Anne van Kesteren
http://annevankesteren.nl/
Jonas Sicking [mailto:jo...@sicking.cc] wrote:
>On Fri, Jul 2, 2010 at 1:29 AM, Anne van Kesteren wrote:
>> On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky wrote:
>>> On 6/29/10 2:36 PM, Chris Wilson wrote:
See, this is exactly why we asked the question - because it seems
that behavi
* Anne van Kesteren wrote:
>You'd have to read it to figure out what the "event flow" is, for instance.
Which is something that is much more likely to stick with you, yes.
>I disagree. Only Node objects have event flow and the Window object
>interacts with those in a particular way. All other o
On Fri, 02 Jul 2010 12:57:08 +0200, Bjoern Hoehrmann
wrote:
* Anne van Kesteren wrote:
You have to read DOM Events either way.
Not to answer the particular question. Sure, you might have read the DOM
Events specification, say, to figure out what Event.currentTarget is but
what it means when
* Anne van Kesteren wrote:
>On Fri, 02 Jul 2010 12:03:30 +0200, Bjoern Hoehrmann
>wrote:
>> Well let's see: if you want to know what the XHR event flow is, then you
>> have to read the XHR specification to see whether it specifies something
>> different from the "default" regardless of whether i
On Fri, 02 Jul 2010 12:03:30 +0200, Bjoern Hoehrmann
wrote:
Well let's see: if you want to know what the XHR event flow is, then you
have to read the XHR specification to see whether it specifies something
different from the "default" regardless of whether it does or does not.
If it does specif
* Jonas Sicking wrote:
>On Fri, Jul 2, 2010 at 1:29 AM, Anne van Kesteren wrote:
>> On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky wrote:
>>> I think Anne answered the question, in any case: the XHR event target
>>> chain only contains the XHR object itself and nothing else. If the spec
>>> d
On Fri, Jul 2, 2010 at 1:29 AM, Anne van Kesteren wrote:
> On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky wrote:
>>
>> On 6/29/10 2:36 PM, Chris Wilson wrote:
>>>
>>> See, this is exactly why we asked the question - because it seems that
>>> behavior is inconsistent, we're not sure what the ex
On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky wrote:
On 6/29/10 2:36 PM, Chris Wilson wrote:
See, this is exactly why we asked the question - because it seems that
behavior is inconsistent, we're not sure what the expectation is.
Note that the Firefox behavior I described is irrelevant t
On 6/29/10 2:36 PM, Chris Wilson wrote:
See, this is exactly why we asked the question - because it seems
that behavior is inconsistent, we're not sure what the expectation is.
Note that the Firefox behavior I described is irrelevant to
specification efforts, because it's not visible to web pa
On 6/29/10 2:36 PM, Chris Wilson wrote:
See, this is exactly why we asked the question - because it seems that behavior
is inconsistent, we're not sure what the expectation is.
Note that the Firefox behavior I described is irrelevant to
specification efforts, because it's not visible to web p
On Tue, 29 Jun 2010 23:36:28 +0200, Chris Wilson
wrote:
See, this is exactly why we asked the question - because it seems that
behavior is inconsistent, we're not sure what the expectation is. The
fact that the XHR spec says the events do not bubble (but says nothing
about capture) is con
van Kesteren; www-...@w3.org; public-webapps@w3.org; Travis Leithead;
Adrian Bateman; Chris Wilson
Subject: Re: Custom DOM events and privileged browser add-ons; Was:
Bubbling/Capturing for XHR + other non-DOM objects
On 6/25/10 5:56 AM, Brett Zamir wrote:
> I guess in Firefox the document is a
On 6/25/10 5:56 AM, Brett Zamir wrote:
I guess in Firefox the document is all part of
one big tree that includes the add-on markup, so propagation is indeed
within the same DOM tree
It's not, actually. In Firefox, an event will bubble from a Window to
some object in the browser UI associated
On 6/25/2010 5:09 PM, Anne van Kesteren wrote:
On Wed, 23 Jun 2010 01:53:51 +0200, Travis Leithead
wrote:
This topic came up internally on the IE team, and we thought it would
be noteworthy to put this question before the working groups in hopes
of getting a spec clarification made.
The ques
18 matches
Mail list logo
