Mrunal, Do we, or will we have with new rebase version, all the necessary pieces in place in blink/chromium to implement the vibra? That is, we don¹t need to cherry pick anything from upstream. Last think I checked all the necessary pieces where not in place in our trees.
The issue you refer to seems to be closed on 28.Oct.13 which would indicate we get all the necessary code in our rebase now, right? BR; Sakari On 11/14/13, 4:39, "Kapade, Mrunal" <[email protected]> wrote: >Summary: This feature will enable the Vibration API for Crosswalk in >Tizen. >Affected component: content/renderer and few others >Jira ID: https://crosswalk-project.org/jira/browse/XWALK-294 >Target Release: Crosswalk v3 > >Implementation details: Vibration API has already been implemented and >shipped in Chromium upstream, as can be seen here, >https://code.google.com/p/chromium/issues/detail?id=222504. >This implementation aims to hook-up the Vibration API to the native Tizen >API. More information about the Tizen Vibrator API can be found here, >https://developer.tizen.org/help/index.jsp?topic=%2Forg.tizen.native.apire >ference%2FclassTizen_1_1System_1_1Vibrator.html > >W3C Spec can be found here, http://dev.w3.org/2009/dap/vibration/ > >Thanks, >Mrunal >_______________________________________________ >Crosswalk-dev mailing list >[email protected] >https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
