On Thu, Apr 23, 2015 at 4:13 AM, Hallvord Reiar Michaelsen Steen
hst...@mozilla.com wrote:
We're exploring text/html paste behaviours in Mozilla bug 586587 [1] and
running into some tricky questions I'd like to discuss here.
Basically, on Windows IE and other apps that write HTML to the
Has anyone ever proposed exposing the structured clone algorithm directly
as an API? Katelyn Gadd was musing about fast deep copy in JS on Twitter,
and I proposed a hack to use postMessage to do so[1], which works but it's
a little roundabout. Since structured clone is a primitive that the web
On Thu, Apr 9, 2015 at 5:15 PM, Ashley Gullen ash...@scirra.com wrote:
Why doesn't the Gamepad API fire events for button pushes or axis
movements? For example when pressing a mouse button or moving the mouse the
browser fires mousedown and mousemove. The Gamepad API however requires
you to
Hello,
The Gamepad spec has been languishing for some time, and I take
responsibility for that. However, on the bright side we have two
implementations shipping (Firefox, Chrome), and another shipping in
previews (IE) that, while not completely compatible, are usable in a
compatible manner, which
On 10/22/2014 8:08 AM, Arthur Barstow wrote:
* Gamepad: Ted and Scott; plan and expectations to get the spec to
feature complete state (aka Last Call) and implementation status.
Sorry about the late response, I had a vacation in the middle of things
there.
The Gamepad spec currently has one
On 10/13/2014 3:03 AM, Chad Austin wrote:
Just as I mentioned in my previous email to this list, I recently was
asked to review the Gamepad API draft specification. My background is
games though I've done some scientific computing with alternate input
devices too.
On 4/30/2014 12:21 AM, Glenn Maynard wrote:
My original prototype provided the events mentioned above. The
feedback I received was overwhelmingly in favor of a polling API
instead[3]. I decided to go ahead with that (actually Scott beat
me to the punch and implemented that in
On 4/29/2014 10:39 AM, Ted Mielczarek wrote:
The only major issue that needs to be fixed in the Gamepad API spec
currently is the liveness of Gamepad objects[1].
After reading through the discussion here I'm leaning towards specifying
the snapshot behavior that Chrome implements. Regardless
The only major issue that needs to be fixed in the Gamepad API spec
currently is the liveness of Gamepad objects[1].
Currently this is implemented differently in Firefox and Chrome--Firefox
uses live Gamepad objects, in that you can take the .gamepad property
from a GamepadEvent or a Gamepad from
On 4/29/2014 1:34 PM, Brandon Jones wrote:
I don't think that API design should be driven by implementation
details, but it may be useful to provide some background on Chrome's
Gamepad implementation here:
The current polling-only API Chrome uses is largely due to
practicality with the
of it with
the snapshot model in mind.
On Tue, Apr 29, 2014 at 9:39 AM, Ted Mielczarek t...@mozilla.com
mailto:t...@mozilla.com wrote:
snapshots and see what's changed. (Additionally as an implementation
detail this maps very well to the Windows XInput API, which is a
polling-based API.)
You
On 4/29/2014 7:35 PM, Oren Freiberg wrote:
Originally I was leaning towards live model but I am now leaning towards a
snapshot model being the better option. We also found that there was added
overhead with making the values live. Having had a few developers play around
with both the idea
Hello,
We've decided that the Gamepad spec is feature-complete at this point.
We'll be doing some polish work to get it moving to last call status,
but new features will be pushed out to a v.next. In light of this we've
created a wiki page[1] to gather potential features for a future spec
On 4/4/2014 8:40 AM, Arthur Barstow wrote:
Re testing, are you and/or Scott going to submit tests? If not, is
there someone else that can help/lead the testing effort?
I don't have any non-Mozilla-specific tests currently, and the
Mozilla-specific ones I have are not feasible to use
On 4/4/2014 10:06 AM, Florian Bösch wrote:
On Fri, Apr 4, 2014 at 3:45 PM, Kostiainen, Anssi
anssi.kostiai...@intel.com mailto:anssi.kostiai...@intel.com wrote:
In the initial versions of the spec we indeed considered such
reuse. Here's my recent summary:
On 3/24/2014 3:55 PM, Florian Bösch wrote:
I might point out that haptic feedback devices are alive and well:
snip
There's a few more outputs than speakers though, for instance:
snip
I'd note that all of the devices you've mentioned fall way out of the
scope of what we're trying to cover
On 4/2/2014 7:05 AM, Arthur Barstow wrote:
* Gamepad: Ted and Scott; plan and expectations to get the spec to
feature complete state (aka Last Call) and implementation status
Implementation status:
Firefox and Chrome both implement the current ED with a few minor
inconsistencies--Chrome has
On 3/24/2014 1:04 AM, Brandon Jones wrote:
Mozilla has played around with gamepad vibration a bit
already: https://bugzilla.mozilla.org/show_bug.cgi?id=680289
There's been some mixed messages, but so far the basic idea seems to
be to either extend the existing Vibration API
On 4/3/2014 12:05 PM, Florian Bösch wrote:
Every controller is an assemblage of input and output hardware. It's
vastly much easier to to oversee what kind of devices you'll get which
are:
* Buttons (down or up)
* Axes (scalar value)
* Rumbles (speed)
* Motors (negative/positive
On 3/14/2014 11:36 AM, Patrick H. Lauke wrote:
On 14/03/2014 15:29, Vincent Scheib wrote:
Perhaps I'm missing some context. What issue are you raising that isn't
handled by the gamepad API [1]?
[1] https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html
The issue is perhaps
On 2/20/2014 1:35 PM, Brandon Jones wrote:
I've been working with the Gamepad API implementation in Chrome
recently, trying to bring it up-to-date with the latest editors draft
of the spec
(https://dvcs.w3.org/hg/gamepad/raw-file/default/gamepad.html). While
generally I feel like it's a good
On 10/14/2013 3:34 PM, Marcos Caceres wrote:
Hi All,
The Gamepad API was briefly discussed at the LXJS conference.
See:
http://www.youtube.com/watch?v=ekvaKmVfjtct=5m30s
It seems at least one developer is very unhappy with it.
Have we received any other feedback from developers about
On 10/2/2013 12:31 PM, Arthur Barstow wrote:
Hi Ted, Scott,
If any of the data for the Gamepad spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec -
last published 29-May-2012 - or the spec's status with respect
On 8/5/2013 1:11 PM, Tab Atkins Jr. wrote:
On Thu, Aug 1, 2013 at 2:31 AM, Mikkel Staunsholm staunsh...@gmail.com
wrote:
Any comments on that?
Should it resemble the vibrations api more (with patterns, and turning it
off by setting strength to 0)?
Should it be in the vibrations api instead
On 5/2/2013 12:23 PM, Florian Bösch wrote:
I'd like to note that the current semantic (in google chrome) of
press button to connect device is not very user friendly. Not all
buttons register as buttons (some register as axes) and won't do
anything. Some devices are also devoid of buttons (like
Hello there,
The Gamepad spec hasn't seen a lot of activity lately, and it's
primarily my fault. I got tied up in other work and didn't have time to
work on my implementation in Firefox or the spec. I dug out of that and
managed to land an initial implementation which is currently available
in
On Wed, Sep 26, 2012 at 10:27 AM, Arthur Barstow art.bars...@nokia.com wrote:
* Gamepad - Scott, Ted - what's the status of the spec and its
implementation?
We probably need to discuss a bit more, but I think the spec is pretty
close to a first version. The one large issue that we haven't
On Thu, Jul 26, 2012 at 9:20 PM, Scott Graham scot...@chromium.org wrote:
There's no particular indication at the spec level to indicate stopping the
gamepad polling, based on the assumption that it's an implementation detail.
Maybe there should be some way for content to hint that though?
I
28 matches
Mail list logo
