Hi, Crosswalk keeps same behavior like Android system. If the video could be played Android native application, it will be in Crosswalk. So I suggest to check fragment mp4 playback behavior by native video player on Android 4.3, if met the same issue, then this is platform capability issue.
Also out of curiosity, why using fragment MP4? If it’s used for adaptive streaming, maybe media source API could be a better option? https://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html Thanks, Changbin ________________________________ From: Crosswalk-help [[email protected]] on behalf of David Covey [[email protected]] Sent: Tuesday, November 18, 2014 1:20 AM To: [email protected] Subject: [Crosswalk-help] Video element + fragmented mp4 behavior inconsistent Hi All - I'm experimenting with Crosswalk as a platform for delivering a consistent android experience for an HTML5 based app delivering h264 video as a fragmented mp4 through a video element. While I wasn't sure what to expect, I was surprised to get different results across android versions. On android 4.4 and up, crosswalk plays both normal and fragmented mp4 normally, just as the default android browser does on these devices. On a 4.3 device, a standard mp4 plays relatively normally, but a fragmented mp4 loads and then stalls when it attempts to play. My understanding is that chromium doesn't support mp4 by default in the first place, so I imagine there is something I'm missing about how crosswalk's chromium implementation handles video thats giving me these results. If anyone could help me understand whats going on under the hood a bit, and why crosswalk isn't giving consistent behavior here, I would really appreciate it! Thanks! _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
