[July 1-3] [face to face] Agenda?

2008-05-11 Thread Jean-Yves Bitterlich
Hello, I understood that prio 1 item on the july 1st-3rd agenda is going to be XHR2 (XDR... input). What other items are (known to be) on the agenda ? (probably 3 days are anyway just enough to finalize XHR) regards, -jy

Re: [Element Traversal LC] access to element by index

2008-04-09 Thread Jean-Yves Bitterlich
Jonas Sicking wrote: Jean-Yves Bitterlich wrote: A few alternatives were proposed here, referred below as (i) 'attribute NodeList childElements', (ii) 'Node item(index)' and (iii) xpath .querySelector. I personally like (iii) because it is powerful (or is it ju

Re: [Element Traversal LC] access to element by index

2008-04-08 Thread Jean-Yves Bitterlich
Hopefully, not too late to bring some more 'Elements' (at least our opinion) to this thread and spec. As some of you already know, we have brought JSR-280 [1] (parts of which is DOM related and refer to the ElementTraversal (draft) specification) to a Final Release back in October 2007. T

Re: ISSUE-119: names lengthComputable and total

2007-12-10 Thread Jean-Yves Bitterlich
Maciej Stachowiak wrote: On Dec 10, 2007, at 8:17 AM, Jean-Yves Bitterlich wrote: Maciej Stachowiak wrote: On Dec 10, 2007, at 7:15 AM, Charles McCathieNevile wrote: Ikivo have told me that they also implemented already with the

Re: ISSUE-119: names lengthComputable and total

2007-12-10 Thread Jean-Yves Bitterlich
5 Nov 2007 21:34:50 +0100, Jean-Yves Bitterlich <[EMAIL PROTECTED]> wrote: Hi, To the question in ISSUE-119 whether "[...] they already get implemented with these names somewhere?", the answer would yes given that the Final Release of "JSR-280 XML

Re: [ElementTraversal] Remarks on http://dev.w3.org/cvsweb/~checkout~/2006/webapi/ElementTraversal/publish/ElementTraversal.html?rev=1.10

2007-10-22 Thread Jean-Yves Bitterlich
Innovimax SARL wrote: http://dev.w3.org/cvsweb/~checkout~/2006/webapi/ElementTraversal/publish/ElementTraversal.html?rev=1.10 s/provides a attribute/provides an attribute/ s/english/English/ Why is "element" not written "Element" ? same for "text" ? Isn't "ChildrenElementsCount" better

Re: CSS Query API: selectorQuery(...)

2007-07-20 Thread Jean-Yves Bitterlich
+0.9 Robin Berjon wrote: On Jul 19, 2007, at 19:07, Bjoern Hoehrmann wrote:   The WebAPI Working Group is considering to conduct a poll to finally put the method naming issue in the CSS Query API specification to rest; Charles asked us to propose alternatives to selectElement/s

Re: [selectors-api] The Naming Debate

2007-06-27 Thread Jean-Yves Bitterlich
ric    selector language."   -- http://lists.w3.org/Archives/Public/public-webapi/2007Jan/0044.html * "1) css is not a verb 2) this sounds like it would return style    declarations, not elements."   -- http://lists.w3.org/Archives/Public/public-webapi/2007Jan/

Re: DOM L3 Spec

2007-04-27 Thread Jean-Yves Bitterlich
makes sense. I just updated the table with those defined in ProgressEvent. maybe we could extend the wiki your sent to have a table similar to that in DOM3-Events to avoid consistency issues when creating new events... -j Bjoern Hoehrmann wrote: * Jean-Yves Bitterlich wrote

Re: Progress events being cancelable?

2007-04-27 Thread Jean-Yves Bitterlich
in the same context the "bubbling phase" needs to be reviewed for Abort and Error; both are Bubble=Yes in DOM3 and No in Progress Event. loadstart and progress may already exist in other specification and probably need also synchronization ... -j Jean-Yves Bitterlich wrote: +1

Re: Progress events being cancelable?

2007-04-27 Thread Jean-Yves Bitterlich
anyway, but if there is, such as informing the user that a transaction is in progress there are lots of drawbacks to canceling that and no clear benefit to justify keeping it cancelable. cheers Chaals -- Jean-Yves Bitterlich Senior Staff Engineer

DOM L3 Spec

2007-04-25 Thread Jean-Yves Bitterlich
gressEvent } { ||progress, ||No, Yes, ||Element, ||ProgressEvent } { error, ||No, Yes, ||Element, ||ProgressEvent } { abort, ||No, Yes, ||Element, ||ProgressEvent } { load, ||No, Yes, ||Element, ProgressEvent ||} | ? -j -- <http://www.sun.com/> *Jean-Yves Bitterlich* Senio

Re: DOM Events

2007-04-11 Thread Jean-Yves Bitterlich
dispatched correctly. Again (our feeling) is that the specification sounds like the implementation cannot/should-not dispatch application specific events. -- Jean-Yves Bitterlich, Sun Microsystems GmbH, Sonnenallee 1, 85551 Heimstetten, Germany Amtsgericht München: HRB 161028 Geschäfts

Re: DOM Events

2007-03-29 Thread Jean-Yves Bitterlich
Bjoern, Thanx very much for the prompt reply. here tackling the EventTarget.dispatchEvent point: (see inline) Bjoern Hoehrmann wrote: * Jean-Yves Bitterlich wrote: Method: EventTarget.dispatchEvent(Event evt) It is unclear how to notify an application about incorrect event target

Re: New draft of Progress events spec

2007-03-29 Thread Jean-Yves Bitterlich
ferent types of things that could conform in different ways, and tried to make the structure clearer. Comments welcome, as always. Cheers Chaals -- Jean-Yves Bitterlich Senior Staff Engineer Sun Microsystems GmbH Sonne

DOM Events

2007-03-29 Thread Jean-Yves Bitterlich
ssertion ? I thereby also give permission to forward these requests to w3c. best regards, Jean-Yves -- Jean-Yves Bitterlich Senior Staff Engineer Sun Microsystems GmbH Sonnenallee 1, 85551 Heimstetten, Germany