Ahmed Hassan <hassan....@googlemail.com> writes: > It is very essential to our android port to be able to slow down > videos, but the current release M48 does not support this feature. > However its a very important one and critical for our work. The > feature is added via flag in version M49 for android and it works > great. > > On the chromium issue tracker there is the suggestion to use: chromium > 49.0.2623.7 or higher > There should not be notable issues with this version. See the following > tracker: > > https://code.google.com/p/chromium/issues/detail?id=263654 [...] > I have already forked and rebased the corresponding V8 version: > 4.9.385.5 > (https://github.com/nerdmed/v8-crosswalk/tree/crosswalk-18/49.0.2623.7) > and i would like to push a chromium branch to the upcoming M49 > release. > Is there someone else here interested in doing that or in any other > way willing to support us with this?
Hi Ahmed, Thanks for using Crosswalk, and I'm glad it's been useful so far. I took a look at the Chromium bug you mentioned, and it seems that the feature you need is being implemented as part of a much bigger project (codenamed Spitzer) that's tracked here: http://crbug.com/507834. In practice, this means that the first approach that I was going to suggest, cherry-picking specific commits to M48 to fix the issue without having to move to M49, does not work: it all depends on a number of commits and work that is still being done upstream. Like Dale Curtis said in the bug you referenced, everything still looks highly experimental. Consequently, even if we did find a bunch of commits that implemented the specific functionality you need it would be too risky to enable this for all our users by default. This leaves us with two options here: 1. You guys build a separate Crosswalk fork with the functionality you need. At the very least, it involves looking for all the required commits that landed in upstream Chromium and cherry-picking them on top of M48, then building Crosswalk from source. By the way, I'm not sure if you've seen this before, but we also have some extensive documentation on how we rebase Crosswalk on top of new Chromium releases that can be helpful for you: https://github.com/crosswalk-project/crosswalk-website/wiki/Rebasing-our-forks And of course, if in the end it turns out that you can get your feature with a small number of non-intrusive commits, we'd be more than glad to revisit this and integrate them in our repositories. 2. We get more help to move to M49 faster. I'm assuming you guys don't have problems working with our canaries/betas instead of stable releases. We are tracking the M49 rebase in our JIRA as XWALK-5805, but the work will only start now that we've finished rebasing on top of M48. It is a tiresome process, so more hands definitely makes things go faster. Please let us know if you have additional questions. Cheers, Raphael _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
