Re: ACTION-126: What is DOM3EV about...

On Tue, 04 Apr 2006 15:39:56 +0200, Jim Ley [EMAIL PROTECTED] wrote: Anne van Kesteren [EMAIL PROTECTED] What we should make sure of is that the conformance on specifications section clearly states what is allowed and what is not so that we don't end up with 'mousemove' being incompatible

Re: First Public WD of XMLHttpRequest released

requests seem to be covered by (if any) although HEAD requests need some explicit language somewhere. Mostly for saying readyState goes to 3 first and after that directly to 4. (Which should be clear more or less, but still.) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-58: XMLHttpRequest.abort() should just reset the object

suggested? Not sure if that's appropriate for this version though... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest object suggestion

could be done through scripting it would be solved using an extension on the History object, not the XMLHttpRequest object as the problem is more general than that. However, there are all kinds of security implications which make it a bit of a rat hole... -- Anne van Kesteren http

Re: References in XHR spec

it before publishing, but I never actually made the change... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Small typo

network activity Thanks, this has been fixed on the dev.w3.org version... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-75: Is method case-sensitive?

. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-75: Is method case-sensitive?

in the specification...) Should we specify that methods MUST be treated as case-sensitive knowing that we will than never exit CR state given the way it has been implemented and will stay implemented because of the content that's out there? Those type of questions... -- Anne van Kesteren http

Re: ISSUE-75: Is method case-sensitive?

, although we'd effectively rewrite HTTP for a bit. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-75: Is method case-sensitive?

criteria doesn't solve any of the problems. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest Object feedback

presume). Please raise a separate issue on this. Your comments are much appreciated. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-75: Is method case-sensitive?

). And that's what most content is using... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - Abstract section

client functionality for transferring data between a client and a server. Used that text. Added some abbr too... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - history in Introduction section

the history, - or move it to the status section So you're suggesting to have the make the Introduction section an actual introduction? Might make sense... A subsection on history might be an idea, if people are interested in it. -- Anne van Kesteren http://annevankesteren.nl/ http

Re: [comment] XMLHttpRequest Object - Address Extensibility

scheme.) Company Foo could introduce a codeFooFollowRedirect(varboolean/var)/code method for example./p pAuthors MAY use extension mechanisms specific to the host language, like code.prototype/code in ECMAScript./p -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: No arguments to XMLHttpRequest.send (ACTION-58)

first during the CR phase... So I don't see that as a show-stopper. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - Address Extensibility

really like it either, I was hoping for comments :-) It seems extensibility in the DOM in general is a bit unaddressed. [...] Extension requirements similar to ECMAScript would be a much more logical approach. Pointer? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - clarity of language

, pointers? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - DOM 3 Load and Save

? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - no interoperable implementations

this to the history section, if we really need one (see other reply)? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [XHR] What mime types should trigger XML parsing?

illegal. Any proposals? Personally I don't really care about any of them... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-75: Is method case-sensitive?

. We also haven't decided yet, ISSUE-74, whether or not to allow arbitrary method names. Internet Explorer 7, for one, doesn't support it as has been pointed out earlier. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [comment] XMLHttpRequest Object - Address Extensibility

. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest readystatechange events

Recommendation. It's also that if we don't do it now v2 isn't so much about cleaning up anymore... rather more reverse engineering. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest progress events

., these are new events it would be useful if you stated what type of interface they would implement, what .bubbles and .cancelable are for the event. So far the only things that are clear from your proposal are .type and .namespaceURI... -- Anne van Kesteren http://annevankesteren.nl/ http

Re: handling of POST in XMLHTTPRequest.

for at least XML documents given your test results. Can you still overwrite it though? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest Object feedback

that UAs MAY add. It MUST NOT be overriden? Yes. That's been done. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

correctly) so we can drop StaticNodeList and just define that the object is static. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

that way NodeList would look that way too and I'd therefore suggest raising that on [EMAIL PROTECTED] instead. Note that I don't really want to be defining StaticNodeList in the first place. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest security section draft

://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/publish/XMLHttpRequest.html?content-type=text/html;%20charset=utf-8#security into the editor's version. It probably needs a lot of work... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: First Public WD of XMLHttpRequest released

, and inputEncoding would be a better option than xmlEncoding - if we're assuming the server knows the best format for a document serialisation, but I don't see the point of requiring such behaviour. See ISSUE-83. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-29: how is uri parameter of the open() method resolved

, etc. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest Object feedback

because it has been abused too much in phishing mails. For other schemes where this is perfectly valid, like ftp, it works just fine in Internet Explorer. What does IE does in such cases and do we want the draft to reflect that? -- Anne van Kesteren http://annevankesteren.nl/ http

Re: [comment] XMLHttpRequest Object - no interoperable implementations

this to the history section, if we really need one (see other reply)? Yes it could be a solution And would satisfy your comment? We're planning on doing this for the next draft. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest.abort()

. ... but perhaps it should only say the object is resetted and no new data should be made available to the object or something along those lines. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

ACTION-148: responseText and encoding

. This seems a lot better than how http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/#dfn-responsetext reads at the moment, but I've the feeling I should add some more references. Perhaps [RFC2616] after the first paragraph for entity body etc.? -- Anne van Kesteren http://annevankesteren.nl

Re: Extension HTTP methods

thing. The whitelist would contain all safe methods currently spreaded over various RFCs. Mark Nottingham would report back if the IETF was ok with this approach or not. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest.abort()

On Sun, 14 May 2006 14:00:08 +0200, Ian Hickson [EMAIL PROTECTED] wrote: Currently it says: When invoked, this method MUST cancel any network activity for which the object is responsible and reset the object. That's fine. Ok! -- Anne van Kesteren http://annevankesteren.nl/ http

Re: ACTION-51: XMLHttpRequest and 403

and xhr.responseText is set as normal. A testcase can be found at http://people.mozilla.com/~sicking/testcases/xhr-header.html For XHR2 it would be interesting to know if you invoke .onload or .onerror and if you think that can be changed. -- Anne van Kesteren http://annevankesteren.nl/ http

Re: ACTION-148: responseText and encoding

meeting :-) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XHR constructor example

(in languages that require those), it's generally considerd quite bad practice. Sure, give a me a sensible suggestion and I'll take it. Given recent discussions (you can post as well as retrieve) I'm not sure the original suggestion `var request` makes sense. -- Anne van Kesteren http

ACTION-139: the IDL is non-normative

bindings are normative. Also removed http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/#xmlhttprequest the second editorial note regarding drafting up a note and all that. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

van Kesteren http://annevankesteren.nl/ http://www.opera.com/

XMLHttpRequest request bodies (was: Re: Issue: request bodies)

be to say that the data passed to send() is always used as the entity body, if present, unless the method argument is GET in which case it's dropped. Any objections? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-148: responseText and encoding

that the ... [...] Doesn't really matter, IMHO. References are important when the reader might not know what was being referenced, but for this kind of thing... Fine by me. Thanks for your comments. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

, but we'll see that when we get there. Thanks for raising it on the list. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Issue: Authentication Credentials

this although a bit more abstract in the part about authentication. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

a selector.) Well yeah, and XPath is in DOM Level 3... This is more about providing a simple way of selecting a bunch of modes based on a group of selectors. This functionality is already provided in libraries and people would find this really useful. (As would I!) -- Anne van Kesteren http

Re: ACTION-87: Selectors API

when you get a random element back like event.target. And even in that case you can probably give the event some random ID in most cases but it's not really flexible. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

, people would probably use the shorter name and just take the first node using [0] or whatever can be used for that in their language binding. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHTTPRequest Issue on behaviour when method not supported

, preferably the exception. I'd like to defer this until the whole method discussion has been sorted out. Consider it noted though. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-87: Selectors API

. I'm fine with DOMArray. Let me know when there's something in TR/ I can point to. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

regrets 20060607

Don't have a phone here that actually works. :-( -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [ANN] Selectors API

to myNSResolver.prototype.lookupNamespaceURI for some reason? This is just some text to make people complain. I hope to be able to remove the section... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [ANN] Selectors API

. Fair enough, done that. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XHR constructor example

On Mon, 22 May 2006 12:32:32 +0200, Mark Nottingham [EMAIL PROTECTED] wrote: client. (XHR is a HTTP client API specification). Taken. Thanks. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[DOM3EV] introduce Event.trusted? (ISSUE-10)

it was suggested to http://www.w3.org/mid/[EMAIL PROTECTED] defer this feature indefinitely. The WG hasn't discussed the outcome of this action. First raised on http://www.w3.org/mid/[EMAIL PROTECTED] public-appformats. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-195: mousewheel proposal

of the mousewheel event is to scroll, zoom, whatever in vertical direction. If mousewheel is cancelled it's default action won't happen. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Optional method arguments in the DOM

omitted is specified and it's value to be assumed by the UA is. void() test(foo, [bar] null) Would be a way to do it I guess. (I don't really like the syntax though...) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] Editorial

seem a bit weird so it's now Selectors [Selectors] as suggested. * Typo [[[ Using psuedo-elements … ]]] Could you please tell me what you mean here? (I haven't checked any of the fixes into CVS yet, will do that shortly.) -- Anne van Kesteren http

Re: [selectors-api] DOM Level 3 XPath

to coordinate with the appropriate DOM IG. Did you send an email to [EMAIL PROTECTED] The plan is to push DOM Level 3 XPath to W3C Recommendation from within the Web APIs WG. I assume that satisfies your concern? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] Future work on Extensibility

to defer all that to DOM Level 3 Core at some point. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] Security Considerations and stability

: ]]] What is hostile content? I agree with Ian that this term is sufficiently clear. How do you test the remain stable assertion? Ian has explained this to your satisfaction, right? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] Editorial

On Fri, 04 Aug 2006 18:12:28 -0400, Sander [EMAIL PROTECTED] wrote: Could you please tell me what you mean here? Psuedo should be pseudo. ^^ ^^ Oops, fixed. Thanks! -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Typo in XHR spec

On Mon, 19 Jun 2006 20:49:03 +0200, Alex Vincent [EMAIL PROTECTED] wrote: Under setRequestHeader(), there's a word spelled Destinaion. I believe you want Destination. Thanks, fixed (local copy). -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest conformance comments

. They are changed. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XmlHttpRequest IDL non normative

such a thing. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XHR editorial - UA

it jarring). Shouldn't it be user agent(s) or User agent(s) (at the start of sentence) in that case? Addressed in the local copy. The next public WD (and next revision of the Editor's copy) will have this fixed. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

XMLHttpRequest HTTP methods

have a NOT_SUPPORTED_ERR I suppose. For the user and password and perhaps the uri argument something similar has to be done I guess. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest HTTP methods

On Fri, 11 Aug 2006 14:15:23 +0200, Anne van Kesteren [EMAIL PROTECTED] wrote: I propose that for the open() method we throw a SYNTAX_ERR when the first argument does not match the token production of RFC 2616 and a (not yet defined) SECURITY_ERR when the method is not allowed

ISSUE-39: XMLHttpRequest errors

to suggestions as to how to resolve this issue. (Jim Ley basically brought this up during the first F2F meeting, but I haven't really gotten around to it so far. Sorry about that.) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

ACTION-195: updated mousewheel/mousemultiwheel proposal

. (For example, when using some device without a pointer but with some way to wheel you'd get that.) === -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XBL2 review

On Mon, 21 Aug 2006 23:06:10 +0200, Doug Schepers [EMAIL PROTECTED] wrote: Comments about XBL2 should be directed to public-appformats@w3.org, not [EMAIL PROTECTED] My mistake... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ACTION-195: updated mousewheel/mousemultiwheel proposal

the use case? The rest of the wording seems fine though. The proposal is now in CVS... http://dev.w3.org/cvsweb/~checkout~/2006/webapi/DOM-Level-3-Events/proposals/mousewheel.txt I should probably do something about the line wrapping but I don't really care at the moment. -- Anne van

Re: [selectors-api] Security Considerations and stability

is a very simple and small specification and the security issues being pointed out in the separate section are hopefully widely known already. And if they're not it's not just Selectors API that's affected. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest (re)synchronization

provides. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: cookies and XMLHttpRequest

, discard and send cookies (as received in the Set-Cookie and Set-Cookie2 response headers, and sent in the Cookie header) as applicable. ... and the specification has HTTP in its name. I think it's clear enough and the WG agrees, fwiw. -- Anne van Kesteren http://annevankesteren.nl

Re: [selectors-api] Introduction with more background

of it. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: About XMLHttpRequest Draft

something like: An UA with a HTML implementation, may support additionally text/html, the Document node may have properties related to DOM HTML.. XMLHttpRequest 2. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

ACTION-209: dblclick

it says not more than it should say. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest state after a send()

the latter makes more sense and I tend to agree. It also means you can easily switch between async and sync requests. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-85: Where to define XPathNSResolver?

a typedef or an empty interface... Anyone with strong opinions on this? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest.setRequestHeader with non-ASCII strings

(temporarily, at least): Thanks for this. We decided that it would make the most sense to throw an exception (SYNTAX_ERR) if the header or value doesn't match the production given in HTTP. This is the same for getResponserHeader, obviously... -- Anne van Kesteren http://annevankesteren.nl/ http

Re: XMLHttpRequest test suite suggestion

.htm http://tc.labs.opera.com/apis/XMLHttpRequest/open/009.htm http://tc.labs.opera.com/apis/XMLHttpRequest/open/010.htm I welcome other variants to this story. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: ISSUE-86: Throw INVALID_STATE_ERR everywhere, don\'t or some mix?

on group discussion. Pending feedback it will probably be in the next WD. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest test suite suggestion

that wasn't. It's not really clear to me what the problem with the definition is. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Cross-site extensions for XMLHttpRequest (XXX...)

. If it some point people feel it takes too long I can try to find a gap. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest test suite suggestion

look forward to having to study ECMAScript. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Overriding userinfo in XHR.open()

. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] DOM Level 3 Core + Selectors API

On Wed, 27 Sep 2006 08:57:33 +0200, Karl Dubost [EMAIL PROTECTED] wrote: I agree with your sentence, but please be sure to have the same prose in both sections or to refer to extensibility section. Could you be more specific? I'm not sure what you're hinting at. -- Anne van Kesteren http

Re: HTTP Method list in new XMLHttpRequest draft

on the member list (should've been here) about removing them again as it already states that they SHOULD be supported and they have not much to do with XMLHttpRequest at all. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest test suite suggestion

, the constructor must resolve it using window.document.baseURI of its associated window object as a base. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest test suite suggestion

to the window where the constructor is defined upon (that you call). (I hope I phrased that more or less correct. If not, see the other e-mail.) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: comments on Selectors API WD

SARL becoming a W3C member on the 1st of October, we are ready to help on this specification. If you could provide a testsuite, that'd be cool! -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: comments on Selectors API WD

the CSS WG define scoped selectors. I don't think the Web APIs WG should define that. This API isn't set in stone, there will be a version 2 if there's sufficient demand and need. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: comments on Selectors API WD

. Your WG and the CSS WG could probably solve this quickly. I'm happy for the CSS WG to suggest something sensible. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: HTTP Method list in new XMLHttpRequest draft

and HEAD as well. HEAD is mentioned on multiple other locations and the other two are relevant for the case-insensitive matching. I'm about to check this in into the editor's draft. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [selectors-api] Introduction with more background

developers to understand the benefits of the technology. Please update the introduction. Fair enough, done. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: XMLHttpRequest: Why list HTTP method names

this has been changed to GET, POST, PUT, DELETE and HEAD. All others should be supported, but are not explicitly listed. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: Fwd: Liaison from JSR-287/280

as well makes sense. 2. ProgressEvent This would be part of a separate specification having both progress and uploadProgress (or similar names). -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

  1   2   3   4   >