Closed
Bug 1061917
Opened 10 years ago
Closed 10 years ago
The HTML5 video full screen animation is pretty jarring
Categories
(Core :: Widget, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1105939
People
(Reporter: ehsan.akhgari, Unassigned)
References
(Blocks 1 open bug)
Details
This is very visible on youtube, but <http://camendesign.com/code/video_for_everybody/test.html> probably gives a better test case. Both Chrome and Firefox seem to reflow the video during the full screen transition visibly. They also pause the video playback during the transition. This is very suboptimal compared to the Flash implementation of full screen video.
Safari seems to do things much better, they keep the video playing during the transition, and there are no visible reflows during the transition either.
Comment 1•10 years ago
|
||
Fullscreen bugs normally live in DOM: Core.
Patches accepted.
Component: Video/Audio → DOM: Core & HTML
Comment 2•10 years ago
|
||
(In reply to Chris Pearce (:cpearce) from comment #1)
> Fullscreen bugs normally live in DOM: Core.
Yes, but this is OS X specific. We use the OS X fullscreen transition there and that leads to this issue, as best I can tell. Moving to Widget::Cocoa.
Markus/Steven, is there some way we can avoid the transition just for video fullscreens (as in, does Apple let us do that)?
Component: DOM: Core & HTML → Widget
Flags: needinfo?(mstange)
Comment 4•10 years ago
|
||
I feel like I've answered this question before ;-)
(In reply to Markus Stange [:mstange] from bug 1105939 comment #2)
> Safari doing it means its possible to use a custom animation, but I don't
> know how much work that would be.
Flags: needinfo?(mstange)
Comment 5•10 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #4)
> I feel like I've answered this question before ;-)
>
> (In reply to Markus Stange [:mstange] from bug 1105939 comment #2)
> > Safari doing it means its possible to use a custom animation, but I don't
> > know how much work that would be.
D'oh. Duping there because of the summary and because it's actually in the right component...
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•