New issue
Advanced search Search tips

Issue 921890 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Feature

Blocking:
issue 879966



Sign in to add a comment

Feature request? Disable/interrupt <video controls ..> loading animation

Project Member Reported by tapted@chromium.org, Jan 15

Issue description

Chrome Version       : 70.0.3538.102


I've spun this out of  Issue 917327  to loop in Blink media owners.

Note we're working towards a unified UX for media consumption on CrOS. Regardless of how that takes shape, I think it would be nice to use the standard set of <video controls>. As highlighted in  Issue 917327 , one annoyance is that the loading animation is not interrupted once the video is ready to play. Instead, it completes the current iteration, which may go for a whole second.

A dodgy fix may be to add the 'controls' attribute after some delay - that seems to prevent the loading spinner appearing in some cases, but also means video controls to not appear until mouse hover.

(Maybe Blink/Media folks know of some other workaround).

Alternatively, can we instead interrupt/fade this loading animation as soon as the video loads, rather than allowing it to run to completion?


What steps will reproduce the problem?
1. Load a video from local storage into a <video controls ..> element (i.e. loads quickly=~100ms).

or see  Issue 917327 


What is the expected result?

No loading spinner


What happens instead of that?

Loading spinner animation runs to completion (for ~1 second).

 
Cc: steimel@chromium.org
+steimel@ SWE who has been most active on this code recently.
+amyroberts@, UX for the media controls.

It seems that ideally, we may want to make a call and just not show the spinner if we believe the load will be fast enough. Though, we would need to define how to make that call.

We didn't interrupt the animation on purpose so I don't think we would revert this. However, if you could disable it, what would be the criterias? Intuitively, we could disable it for all local playbacks but are we certain they are all fast to load?

(Interestingly, I just tried to load a local video in Chrome media document and I couldn't see the spinner. I guess the reason is that we autoplay the video, though.)
Labels: Needs-Milestone

Comment 4 by susan.boorgula@chromium.org, Jan 17 (5 days ago)

Labels: -Pri-3 Triaged-ET Target-73 M-73 FoundIn-71 FoundIn-73 FoundIn-72 Pri-2
Status: Untriaged (was: Unconfirmed)
tapted@ Thanks for the issue.

As this issue is marked as Feature request, marking this issue as Untriaged for further updates from Dev.

Thanks..

Sign in to add a comment