[Bug 16707] user/password set to undefined means missing

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16707

--- Comment #3 from Boris Zbarsky <bzbarsky@mit.edu> 2012-04-12 17:05:36 UTC ---
Right.  The big question is whether explicit null passed should mean "missing".
 If it should, then we should have a nullable string here with null as default
value and just have the prose talk about null.  If it should not, then we
should use [TreatUndefinedAs=Missing], probably have this be a non-nullable
string, and the prose should talk about missing arguments.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 12 April 2012 17:05:45 UTC