This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the request section, components of a request were described individually along with their defaults, but in the Response section status, status message, location, headers, and body are first given, and their defaults later defined. It would be better if each response component was defined in the same way as request (i.e., individually, with the defaults).
Same applies to network error... just move the default up to the same line as the one that defines network error.
That doesn't seem entirely right, since network error is just a response whose type is error. Maybe defining request similarly to response would be better?
(In reply to comment #2) > That doesn't seem entirely right, since network error is just a response > whose type is error. > > Maybe defining request similarly to response would be better? I prefer Request the way it is because it makes it easy to look up all the defaults in one place. However, Response is small enough at the moment that it's not a burden to skim down and find the defaults and possible values.
I have more or less done this now. Feel free to suggest further tweaks.