Regarding the vibration portion of the API, I'm still not sure how much
control we should provide. Don't want to get too closely tied to any
specific native implementation. To that end I've put together a brief
document comparing the APIs that I'm aware of:
https://docs.google.com/document/d/1Ms4RF
On Mon, Apr 25, 2016 at 1:06 PM, Bang Seongbeom
wrote:
> It would be good to restrict custom element's name to start with like
> 'x-' for the future standards. User-defined custom attributes; data
> attributes are also restricted its name to start with 'data-' so we can
> define easily new standa
On Mon, Apr 25, 2016 at 10:06 AM, Bang Seongbeom
wrote:
> It would be good to restrict custom element's name to start with like
> 'x-' for the future standards. User-defined custom attributes; data
> attributes are also restricted its name to start with 'data-' so we can
> define easily new standa
It would be good to restrict custom element's name to start with like
'x-' for the future standards. User-defined custom attributes; data
attributes are also restricted its name to start with 'data-' so we can
define easily new standard attribute names ('aria-*' or everything
except for 'data-*
Lots of good feedback! Replies inline.
> Do we want to know the value of the press? Does the API for the Steam
Controller, for example, return the force of the press as a float?
> Likewise, Pointer Events have "pressure"
GamepadButton already has a "value" property, which I think would be
appropr
From: Brandon Jones [mailto:bajo...@google.com]
> readonly attribute Float32Array? position;
Just as a quick API surface comment, Float32Array? is not a very good way of
representing a vector (or quaternion). You want either separate x/y/z/w
properties, or to use a DOMPoint(ReadOnly).
Web VR
On Mon, Apr 25, 2016 at 4:31 AM, Chris Van Wiemeersch
wrote:
>
> If you take a look at all the content libraries out there for the Gamepad
> API, there's a ridiculous amount of logic and special casing web developers
> are having to do just between the Firefox and Chrome implementations - and
> be
On 25/04/2016 03:31, Chris Van Wiemeersch wrote:
Do we want to know the value of the press? Does the API for the Steam
Controller, for example, return the force of the press as a float? The
reason I ask is because with Touch events, there's a `force` property on
the `Touch` interface:
https://dev
Do we want to know the value of the press? Does the API for the Steam
Controller, for example, return the force of the press as a float? The
reason I ask is because with Touch events, there's a `force` property on
the `Touch` interface:
https://developer.mozilla.org/en-US/docs/Web/API/Touch/force