16707 2012-04-12 07:07:46 +0000 user/password set to undefined means missing 2012-10-11 10:08:14 +0000 1 1 1 Unclassified WebAppsWG XHR unspecified PC All RESOLVED FIXED P2 normal --- 1 annevk annevk bzbarsky cam jonas julian.reschke mike public-webapps public-webapps-bugzilla oldest_to_newest 66630 0 annevk 2012-04-12 07:07:46 +0000 When the user/password arguments are set to undefined they should be treated as missing arguments. Either via an IDL option or because that is what undefined means per ES/IDL. 66641 1 cam 2012-04-12 07:42:40 +0000 If we don't change Web IDL due to http://lists.w3.org/Archives/Public/public-script-coord/2012AprJun/0105.html then bang a [TreatUndefinedAs=Missing] on those two arguments. If we do change Web IDL, then [TreatUndefinedAs=Missing] will disappear and it'll just be the default behaviour. I wonder what the behaviour should be if undefined is specified for username but not for password. 66643 2 annevk 2012-04-12 07:50:28 +0000 The other alternative here is that since undefined becomes null per IDL we could maybe make null mean missing in prose. Currently user/password are a bit of a mess because of bug 10326 and to a lesser extent bug 15418. If someone could explain what we should do for them that would be nice. 66668 3 bzbarsky 2012-04-12 17:05:36 +0000 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. 75958 4 annevk 2012-10-11 10:08:14 +0000 This is fixed as suggested in comment 3 by bug 17242 comment 16.