27549 2014-12-09 17:25:22 +0000 Support holes or undefined values in the sequences as return values? 2014-12-09 18:59:51 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC Linux NEW P2 normal --- 26181 1 bugs cam bzbarsky d mike public-script-coord ted public-webapps-bugzilla oldest_to_newest 116054 0 bugs 2014-12-09 17:25:22 +0000 Gamepad spec might want to be able return sequences which have holes. sequence<optional FooBar> as a return value could be quite readable. 116056 1 d 2014-12-09 17:26:45 +0000 HOLES ARE EVIL. Just use undefined instead? 116057 2 bzbarsky 2014-12-09 17:30:12 +0000 > HOLES ARE EVIL. Tell that to UA authors, who all produced arrays with holes here. :( But yes, we could just make it undefined; still need IDL syntax for it, ideally. 116060 3 bugs 2014-12-09 17:33:50 +0000 sequence<optional FooBar> leading to an array which doesn't have holes but just values defined to be undefined would be ok to me. 116064 4 ted 2014-12-09 18:59:51 +0000 Olli filed this bug after discussing bug 27549. Right now implementations are mixed on what to do with removed devices in the return value of getGamepads. Firefox returns an array with nulls where they used to be, Chrome returns a GamepadList which does not have the indicies of removed devices as properties (hasOwnProperty returns false for removed indicies), and IE returns a thing that claims to be an Array but also acts the same way (does not have properties for removed indicies). bug 26181 comment 5 describes the behaviors there. I'm okay with changing the spec as long as we can change it to say something that makes sense in terms of web standards, and also isn't incredibly different from current implementations.