- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 27 May 2008 15:15:57 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: Ian Hickson <ian@hixie.ch>, Maciej Stachowiak <mjs@apple.com>, Laurens Holst <lholst@students.cs.uu.nl>, public-webapi@w3.org
Anne van Kesteren wrote: >> FF3 (removing the header) demonstrates that this case (null value) >> either should be left unspecified, or specified with a more useful >> behavior. > > Firefox demonstrates that it is not interoperable with the three other > browsers. It does not demonstrate anything about the need to do this > differently than currently specified. Setting a header to null, and expecting the header to be sent as "null" is a bug. You haven't provided any evidence of clients relying on this. Please do not wire bad API design like this into the spec, even if it's common for Javascript APIs. BR, Julian
Received on Tuesday, 27 May 2008 13:16:41 UTC