HTML5 Video seeking broken in Canary (unless you disable hardware decoding)
Reported by
josh.gr...@gmail.com,
Jul 3 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2787.0 Safari/537.36 Example URL: https://brokedown.net/videotest3.html Steps to reproduce the problem: 1. Play HTML5 video 2. Seek to frame with v.currentTime=x 3. Be sad when video stops playing and cannot be restarted What is the expected behavior? Video should seek to specified frame and play. What went wrong? Video stops playing and cannot be restarted Did this work before? Yes Works in stable (51.0.2704.106 ) Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 54.0.2787.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 Test case works if you disable hardware decoding in chrome://flags which is not exactly a viable workaround.
,
Jul 4 2016
Unable to reproduce the issue on Windows 7 using chrome latest canary M54-54.0.2787.0 even after not disabling hardware decoding, Observed the video is playing fine and able to seek to specified frame and play. josh.grebe@ - Is this issue seen on incognito mode as well? Could you please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser.
,
Jul 4 2016
I tested with a not-logged-in Canary with no extensions. Verified incognito behavior is the same.
,
Jul 4 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 4 2016
I've tested on Win 10 with Canary fresh install and had same result.
,
Jul 6 2016
There are a few bugs that showed up over the weekend for this.
,
Jul 12 2016
I am unable to repro this issue on both Win7+Chrome 54.0.2794.0. I can't repro this issue. There is no problem to seek forward or backward.
,
Jul 12 2016
This appears to have been fixed by 2790.
,
Jul 15 2016
As per comment #8 closing this issue, Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by josh.gr...@gmail.com
, Jul 3 2016