On Mon, Mar 25, 2019 at 10:05 PM wrote:
> > As far as separating the value; it kind of depends on how you
> > implement it; but let's say you were going to use a static uint64_t or
> > something like that. Instead of heaving a static uint64_t, create a
> > Dictionary and look up the uint64_t
On Friday, March 22, 2019 at 9:56:20 AM UTC-7, Martin Thomson wrote:
> On Thu, Mar 21, 2019 at 1:11 PM Tom Ritter wrote:
>
> > Okay, good, not making this data available until the user activity
> > engages with the gamepad/VR controller (mostly) assuages my concerns
> > on this component. My
On Wednesday, March 20, 2019 at 7:10:54 PM UTC-7, Tom Ritter wrote:
> > > > Example 1: Let’s say touchId is currently set to 0 and no fingers are
> > > > touching the touchpad. When a finger touches the touchpad, touchId of
> > > > this event would be 1. As that finger moves around the
On Thu, Mar 21, 2019 at 1:11 PM Tom Ritter wrote:
> Okay, good, not making this data available until the user activity
> engages with the gamepad/VR controller (mostly) assuages my concerns
> on this component. My remaining concern is around the sensitivity of
> axis movement. If I have my
> > > Example 1: Let’s say touchId is currently set to 0 and no fingers are
> > > touching the touchpad. When a finger touches the touchpad, touchId of
> > > this event would be 1. As that finger moves around the touchpad, new
> > > touch events are added with updated coordinates, however,
On Friday, March 15, 2019 at 8:35:41 AM UTC-7, Tom Ritter wrote:
> Thanks for more details on the use case.
>
> On Wed, Mar 6, 2019 at 1:35 AM wrote:
> >
> > On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> > > To add to Dan's comments here...
> > >
> > > Assuming that
On Fri, Mar 15, 2019 at 11:35 AM Tom Ritter wrote:
> Thanks for more details on the use case.
>
> On Wed, Mar 6, 2019 at 1:35 AM wrote:
> >
> > On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> > > To add to Dan's comments here...
> > >
> > > Assuming that I'm reading
Thanks for more details on the use case.
On Wed, Mar 6, 2019 at 1:35 AM wrote:
>
> On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> > To add to Dan's comments here...
> >
> > Assuming that I'm reading this correctly [1], the fingerprinting risks are
> > pretty extreme
On Monday, February 25, 2019 at 4:17:29 PM UTC-8, Martin Thomson wrote:
> To add to Dan's comments here...
>
> Assuming that I'm reading this correctly [1], the fingerprinting risks are
> pretty extreme here. In the touch spec, we have a monotonically increasing
> counter that doesn't appear to
On Wed, Feb 27, 2019, at 6:43 AM, James Graham wrote:
> The current thinking is that hardware interaction APIs which rely on
> mocks to test should specify the API for testing as part of the
> specification (e.g. [1]). So it seems like the same approach could be
> used here.
>
> [1]
On 26/02/2019 22:49, d...@mozilla.com wrote:
On Tuesday, February 26, 2019 at 2:15:57 AM UTC-8, James Graham wrote:
On 25/02/2019 19:44, Daosheng Mu wrote:
web-platform-tests: none exist (and I don't plan to write WPTs but we do
have gamepad mochitest, I will add new tests to cover these
On Tuesday, February 26, 2019 at 2:15:57 AM UTC-8, James Graham wrote:
> On 25/02/2019 19:44, Daosheng Mu wrote:
>
> > web-platform-tests: none exist (and I don't plan to write WPTs but we do
> > have gamepad mochitest, I will add new tests to cover these two new APIs.)
>
> Why do you plan to
--
Daosheng Mu
Software Engineer | Mozilla
d...@mozilla.com
On Tue, Feb 26, 2019 at 1:14 AM Julien Cristau wrote:
> On Mon, Feb 25, 2019 at 8:45 PM Daosheng Mu wrote:
>
>> Is this feature restricted to secure contexts? Nope
>>
>
> Why not?
>
> I agree. I will make it be restricted to secure
On 25/02/2019 19:44, Daosheng Mu wrote:
web-platform-tests: none exist (and I don't plan to write WPTs but we do
have gamepad mochitest, I will add new tests to cover these two new APIs.)
Why do you plan to not write web-platform-tests? I imagine there may be
technical challenges, but we
On Mon, Feb 25, 2019 at 8:45 PM Daosheng Mu wrote:
> Is this feature restricted to secure contexts? Nope
>
Why not?
Cheers,
Julien
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
To add to Dan's comments here...
Assuming that I'm reading this correctly [1], the fingerprinting risks are
pretty extreme here. In the touch spec, we have a monotonically increasing
counter that doesn't appear to be origin-bound in any way. What is the
purpose of this identifier? In the light
Hi Daniel,
We didn't have a chance to discuss privacy issues in Gamepad Extension or
Gamepad API. We were trying to get responses for the Privacy review [1] but
without any updates yet.
Cheers,
[1] https://lists.w3.org/Archives/Public/public-privacy/2018AprJun/0030.html
--
Daosheng Mu
Software
Neither of the words "security" or "privacy" appear in this spec (most w3
web specs have at least a token attempt at a "Privacy and Security
Considerations" section). At a surface glance this appears to add
additional fingerprinting exposure. Have you talked to the privacy team
about ways to
18 matches
Mail list logo
