Progress Events

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Progress Events

Olli Pettay

Hi all,

Because the user agent must support DOM events, the following text
could be removed:
"User agents must ensure that these events trigger event listeners
attached on Element nodes for that event and on the capture and target
phases."
That text is anyway a bit strange, especially when progress events are
used with XHR.

And it would be great to mark chapters to be either normative or
non-normative. And numbering the chapters would be great
too.

-Olli



Reply | Threaded
Open this post in threaded view
|

Re: Progress Events

Charles McCathieNevile-2

On Fri, 23 May 2008 18:25:36 +0200, Olli Pettay <[hidden email]>  
wrote:

> Hi all,
>
> Because the user agent must support DOM events, the following text
> could be removed:
> "User agents must ensure that these events trigger event listeners  
> attached on Element nodes for that event and on the capture and target  
> phases."
> That text is anyway a bit strange, especially when progress events are  
> used with XHR.

The text is a bit strange. It was added in response to Ian's mail saying  
he had difficuly understanding which requirements applied to which  
implementations, as part of the attempt to provide more explicit  
requirements. There is no formal requirement in the current draft that  
user agents implement DOM events - but perhaps that would be a simpler way  
of setting the requirement?

> And it would be great to mark chapters to be either normative or
> non-normative. And numbering the chapters would be great
> too.

I agree, and will do both of these for or before the next public draft.

cheers and thanks for the comments

Chaals

--
Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals   Try Opera 9.5: http://snapshot.opera.com