W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2005

[whatwg] Re: HTTP 205 response

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 26 Apr 2005 08:44:47 +0000 (UTC)
Message-ID: <Pine.LNX.4.61.0504260831060.25513@dhalsim.dreamhost.com>
On Mon, 25 Apr 2005, Boris Zbarsky wrote:
> >
> > Changed to specifically refer to <form> elements.
> 
> I assume the specification somewhere makes it clear that element names 
> in orange (is this a good idea accessibility-wise?) mean <html:*> 
> elements or something equivalent?

The terminology section says:

"Unless otherwise stated, XML elements defined in this specification are 
elements in the http://www.w3.org/1999/xhtml namespace, and attributes 
defined in this specification have no namespace."

...is that enough?

(The orange colour applies to all <code> elements.)


> > > See also https://bugzilla.mozilla.org/show_bug.cgi?id=198309 for some
> > > discussion on the issue.
> > 
> > Did you have any specific comments in mind?
> 
> Yes.  It's not clear which document should be reset when the 205 
> response is received if the form had a target attribute.  Note that if 
> that happened the 205 may be received after the original document no 
> longer exists.  Also note that in the simplest and most straightforward 
> implementation of form submission (as just another load in a window) the 
> HTTP request may only be aware of the target document, not the one it 
> was "dispatched from" (whatever that means, in general; see next 
> paragraph).
> 
> One other thing.  When a 205 is received, will the onreset handlers of 
> the relevant forms fire?

Addressed the above points.

   http://whatwg.org/specs/web-forms/current-work/#form-submission

Let me know if you can find any other holes! :-)


> It's also not clear what should happen if a 205 response is received in 
> response to an HTTP request that is NOT a form submission (say a link 
> click, the user typing a URI in the URL bar, a window.open call, etc, 
> etc).  It may be that the specification wishes to leave these cases 
> undefined; it may be worth clearly saying so in that case.

Those cases will be defined in the Web Apps spec in due course, but are 
out of scope of the Web Forms spec. I don't really know where to put the 
note in the WF2 spec; putting it in the middle of the forms submission 
algorithm seems a bit weird (obviously that stuff doesn't apply to things 
other than form submission, it's right in the middle of sections that are 
exclusively about form submission).

Thanks hugely for your input,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 26 April 2005 01:44:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:22 UTC