W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

[Bug 27549] Support holes or undefined values in the sequences as return values?

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Dec 2014 18:59:51 +0000
To: public-script-coord@w3.org
Message-ID: <bug-27549-3890-qoxsFsjzy2@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27549

Ted Mielczarek [:ted] <ted@mielczarek.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ted@mielczarek.org

--- Comment #4 from Ted Mielczarek [:ted] <ted@mielczarek.org> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 December 2014 18:59:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC