Re: ACTION-148: responseText and encoding

2006-05-15 Thread Anne van Kesteren
On Mon, 15 May 2006 01:54:02 +0200, Ian Hickson [EMAIL PROTECTED] wrote: If the codetermreadyState/term/code attribute has a value other than 3 (Receiving) or 4 (Loaded), it MUST be the empty string. it here refers to readyState, which is wrong. Fixed. Otherwise, it MUST be the

ACTION-148: responseText and encoding

2006-05-14 Thread Anne van Kesteren
reponseText now reads: If the codetermreadyState/term/code attribute has a value other than 3 (Receiving) or 4 (Loaded), it MUST be the empty string. Otherwise, it MUST be the fragment of the entity body received so far (when codereadyState/code is 3 (Receiving)) or the entity

Re: ACTION-148: responseText and encoding

2006-05-14 Thread Jim Ley
Anne van Kesteren [EMAIL PROTECTED] On Sun, 14 May 2006 14:25:01 +0200, Jim Ley [EMAIL PROTECTED] wrote: This is another difference that is not compatible with existing implementations, why is the 3 not a SHOULD? to meet the goals of being compatible with existing implementations. Which is

Re: ACTION-148: responseText and encoding

2006-05-14 Thread Anne van Kesteren
On Sun, 14 May 2006 14:35:16 +0200, Jim Ley [EMAIL PROTECTED] wrote: That was your personal opinion, and not a decision by the group... currently I do not believe any of todays user agents could pass a test suite of the XHR object, if that's the case then I think it's difficult to claim

Re: ACTION-148: responseText and encoding

2006-05-14 Thread Jim Ley
Anne van Kesteren [EMAIL PROTECTED] During the F2F (again, minutes are not yet released) the group agreed upon not having this reliable baseline approach as it didn't work out. Aha, great! that makes a lot of stuff simpler! I'm happy with the MUST now I hope that clarifies things and I