On Thu, 06 Apr 2006 11:51:17 +0200, Jim Ley [EMAIL PROTECTED] wrote:
I don't see why responseText MUST be null other than in readyState 3
or 4, why not undefined (e.g. if the firing of the 2 is delayed for
some reason then data could be available) Equally MUST on 3 is
incompatible with
On Apr 05, 2006, at 21:48, Jim Ley wrote:
The responseXML MUST be null if the document is not WF cannot
currently be relied on in implementations, do you want to highlight
that fact?
I think that we agreed that that behaviour was a bug and that we
really should be encouraging null. I
On Wed, 05 Apr 2006 23:35:10 +0200, Robin Berjon [EMAIL PROTECTED]
wrote:
The responseXML MUST be null if the document is not WF cannot currently
be relied on in implementations, do you want to highlight that fact?
I think that we agreed that that behaviour was a bug and that we really
Jonas Sicking [EMAIL PROTECTED]
Jim Ley wrote:
UAs MAY set the Accept-Charset and Accept-Encoding headers and MUST NOT
allow them to be overridden.
No motivation has been provided for the above restriction - I have a use
case in accessibility repair tools where the error is only in a
Anne van Kesteren [EMAIL PROTECTED]
I think that we agreed that that behaviour was a bug and that we really
should be encouraging null. I guess that flagging what implementations
do might depend on how soon the bug is fixed.
Authoring guidelines, I say.
What are authoring guidelines? a
