10336 2010-08-09 22:28:51 +0000 "optional" should be allowed even if subsequent arguments aren't optional 2010-10-28 04:23:39 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED WONTFIX P2 normal --- 1 ian cam mike public-webapps public-webapps-bugzilla oldest_to_newest 37322 0 ian 2010-08-09 22:28:51 +0000 It should be possible to say: void drawImage(in HTMLImageElement image, in float dx, in float dy, in optional float dw, in float dh); ...so that it means the same as: void drawImage(in HTMLImageElement image, in float dx, in float dy); void drawImage(in HTMLImageElement image, in float dx, in float dy, in float dw, in float dh); Basically, have "optional" means that if the argument is omitted, all subsequent ones must be too, but that if it is included, any subsequent arguments up to the next "optional" must be included. Currently, "optional" can't be omitted on arguments after the first with "optional", so the above isn't possible. 41798 1 cam 2010-10-28 04:23:39 +0000 That is in fact what the spec used to allow (with [Optional], a long time ago). I removed it because I deemed it confusing: it looks like you can omit dw but still specify dh. The three overloaded operations make it much clearer, IMO.