W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

[Bug 21434] New: Need to spec liveness of Gamepad objects

From: <bugzilla@jessica.w3.org>
Date: Fri, 29 Mar 2013 13:34:49 +0000
To: public-webapps@w3.org
Message-ID: <bug-21434-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21434

            Bug ID: 21434
           Summary: Need to spec liveness of Gamepad objects
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Gamepad
          Assignee: ted@mielczarek.org
          Reporter: ted@mielczarek.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org,
                    scott.w3bugzilla@h4ck3r.net
            Blocks: 17309

The discussion in bug 17309 made it clear that Scott and I have implemented two
different things in regards to the "liveness" of Gamepad objects. Scott's
Chrome implementation returns a static snapshot of each Gamepad when you
getGamepads(), whereas the Gamepad object attached to the "ongamepadconnected"
event in my Firefox implementation is live: you can get the latest device state
out of it at any time.

We need to decide what the correct behavior here is and spec it.

Obviously I'm biased in favor of my implementation, but I think it does have
one large benefit: we're expecting users to poll Gamepad status in a
requestAnimationFrame loop, so if you're generating new Gamepad objects for
every call to getGamepads() you're going to be generating a lot of garbage.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 29 March 2013 13:34:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 March 2013 13:34:51 UTC