New issue
Advanced search Search tips

Issue 598218 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

HTML5 Video element metadata (videoWidth, videoHeight, duration) not set on loadedmetadata event

Reported by fre...@visionscapers.com, Mar 27 2016

Issue description

Steps to reproduce the problem:
1. Go to http://jsfiddle.net/visionscaper/mgoar4bq/4/
2. Select a video using the Choose files button (a video that is expected to play in Chrome)
3. The message "Video metadata not available :(" will be shown indicating that width, height and/or duration is not set when the loadedmetadata has been fired.

What is the expected behavior?
It is expected that the correct video width, height and duration is available when the loadedmetadata event has been fired. In that case the correct info will be shown in the JSFiddle results window.

What went wrong?
The loadedmetadata event is fired, but the video metadata (videoWidth, videoHeight, duration) is not set on the video element when t's fired the event.

Did this work before? N/A 

Chrome version: 49.0.2623.105  Channel: stable
OS Version: 6.0.1
Flash Version: 

The provided JSFiddle provides the correct behaviour on :
 - Safari iOS
 - Safari Mac OS X
 - Chrome Mac OS X (47.0.2526.80 & 49.0.2623.108)

Both Chrome on Mac and Android continuously fire error events when the src is set back to null.
 
What I forgot to mention. Further debugging showed that the metadata is set on the video element *after* the "playing" event has been fired. Thus, if I would do a setTimeout in a "playing" event handler, delaying the assessment of the metadata e.g. for 1 second, only then is the metadata available.
Cc: krav...@chromium.org
Labels: triage-te
Cc: -krav...@chromium.org
Labels: -triage-te Needs-Feedback
Thanks for logging issue, can you please let us know what device is that (phone name)?

We have observed this issue on:
 * Motorola Nexus 6 (Android 6.0.1)
 * Samsung S6 (Android 6.0.1)
 * OnePlus 1 (Android 5.1.1, Cyanogen OS version 12.1.1-YOG7DAS2K1)
 * HTC LG 3 (Android 4.4.2)

Update to the above list : is should be LG G3, instead of HTC LG 3.

So, we have observed this issue on:
 * Motorola Nexus 6 (Android 6.0.1)
 * Samsung S6 (Android 6.0.1)
 * OnePlus 1 (Android 5.1.1, Cyanogen OS version 12.1.1-YOG7DAS2K1)
 * LG G3(Android 4.4.2)

Project Member

Comment 6 by sheriffbot@chromium.org, Mar 29 2016

Labels: -Needs-Feedback Needs-Review
Owner: krav...@chromium.org
Thank you for providing more feedback. Adding requester "kravula@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Hello @kravula,

Is there any progress in reviewing this bug report?

Thanks,

 -- Freddy Snijder
Owner: qin...@chromium.org
Status: Available (was: Unconfirmed)
Labels: -Needs-Review
Hello,

We are wondering if this bug report has already been reviewed and if a solution is in sight? We really need a stable way to assess video meta data in the chrome browser and appreciate any progress here.


Thank you,

  -- Freddy Snijder
Project Member

Comment 11 by sheriffbot@chromium.org, May 16 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Assigned (was: Untriaged)

Sign in to add a comment