Re: [vibration] Mozilla Vibration API status

On Tue, 3 Jun 2014, at 17:17, Kostiainen, Anssi wrote:
> Hi Frederick, All,
> 
> On 23 May 2014, at 11:07, Kostiainen, Anssi <anssi.kostiainen@intel.com>
> wrote:
> 
> > On 22 May 2014, at 17:20, Marcos <marcos@marcosc.com> wrote:
> > 
> >> On May 22, 2014 at 8:47:28 AM, Kostiainen, Anssi (anssi.kostiainen@intel.com) wrote:
> >>>> [ Do we have some helpful Mozillian lurking on the list who’d  
> >>> like to take this forward? This could be a “good first bug” for  
> >>> someone who wants to get started contributing to the Mozilla  
> >>> codebase. ]
> >> 
> >> Filed bug, marked it as a "good first bug":
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1014581
> >> 
> >> Hopefully we can find someone to fix that soon. Please add yourselves to the cc. 
> > 
> > Thanks Marcos, this started moving fast!
> > 
> > I cc’d myself and offered to help with interpreting the spec if needed.
> 
> Mounir landed a patch [1] (thanks!) to align the Mozilla’s implementation
> with the LC spec [2].
> 
> Now that we have two implementations [4] as per the LC, I suggest we
> start the process for publishing CR, and in parallel to that move forward
> with testing now that we have a Test Facilitator for the spec (thanks
> Zhiqiang!). More on that in another thread.

I updated Mozilla implementation indeed but I haven't modified Gecko's
code to handle the step 5. It's not clear to me why this is required by
the spec. Is there actually a way to test that behaviour? My
understanding is that if vibrate() is called, the previous vibrate()
should be cancelled so step 5 is mostly an implementation detail. Am I
missing something?

-- Mounir

Received on Tuesday, 3 June 2014 09:23:23 UTC