- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 26 May 2008 13:15:49 +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: > On Mon, 26 May 2008 12:18:34 +0200, Ian Hickson <ian@hixie.ch> wrote: >> I do think that setting the header to the empty string (as if "" had been >> passed instead) is better behaviour, from an author's point of view. If >> that would resolve this issue then that seems like a good choice. > > As far as I can tell three out of four browsers stringify to "null" / > "undefined" for arbitrary headers and since authors should pass a string > anyway I really don't think it's worth changing this. That behavior simply is not useful, and likely will hide bugs. FF3 (removing the header) demonstrates that this case (null value) either should be left unspecified, or specified with a more useful behavior. BR, Julian
Received on Monday, 26 May 2008 11:16:44 UTC