Closed Bug 790126 Opened 13 years ago Closed 12 years ago

Built-in controls for <video> doesn't have ability to go to fullscreen mode

Categories

(Core :: Audio/Video, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 704229
blocking-kilimanjaro +
blocking-basecamp -
Tracking Status
fennec 31+ ---

People

(Reporter: sicking, Assigned: wesj)

References

Details

(Keywords: productwanted, uiwanted)

+++ This bug was initially created as a clone of Bug #762730 +++ When the play button of a <video controls> element is clicked by the user we should go to fullscreen mode automatically on small-screen devices such as what's used for basecamp. We might also want to do this for fennec, but I'll leave that up to whoever writes a patch here.
For what it's worth, I don't think this is a blocker.
What's the behavior today? Controls and additional UI are present?
I believe so. Controls are present with has a button to go into fullscreen mode. Note that this bug is about <video> elements in webpages (and in apps). It's not about what the video or gallery apps do.
I agree if full screen can be user initiated, this is not a blocker.
Full screen can be initiated in the video / gallery apps. Full screen cannot be initiated when browsing on the web and playing a video, unless the web site is using a web library like popcornjs. The user experience is that you can either turn controls on or off. Neither has the ability to go fullscreen. You can go fullscreen by writing your own set of controls, and building a way to trigger a fullscreen request (mozfullscreen).
Ouch. Definitely seems like a problem that the built-in controls doesn't have the ability to go fullscreen at all.
Summary: Go to fullscreen mode when built-in controls are used to play video → Built-in controls for <video> doesn't have ability to go to fullscreen mode
I thought we support this on Desktop today already?
We do. But I think we use a different set of built-in controls on mobile devices to accommodate for the small screen.
I assume this is the same in Fennec?
Based on Fennec having the same behaviour, not blocking for basecamp. Re-nom if that's incorrect :)
blocking-basecamp: ? → -
Andrew possibly we should consider that the use case is different here, in that on android playing videos is done by an app launching an activity. And the video app will handle the playing off the video. The question in the Mozilla ecosystem is whether we would rather devs call an activity to play a video, or embed the video within their site. I imagine they will go for the easier of the two. Not sure we should model this after fennec. For me it was very difficult to view hd videos as there was no full screen and the video size was larger than screen size. "pinch and zoom" did not work in this scenario. Other thoughts on the matter would be good.
I don't think we'll ever need to force developers to display the video in a separate app. It's pretty easy for a website to make the video go fullscreen when the user starts to play it. Even when using built-in controls.
(In reply to dclarke@mozilla.com [:onecyrenus] from comment #11) > For me it was very difficult to view hd videos as there was no full screen > and the video size was larger than screen size. "pinch and zoom" did not > work in this scenario. This seems like a bug of its own.
This bug now means users can't choose to play YouTube videos embedded on other sites in full screen, see last dup.
This is a really bad experience for users. https://support.mozilla.org/en-US/questions/984287
tracking-fennec: --- → ?
Flags: needinfo?(deb)
Ok, Ian and I chatted and we do want to do a button for this. Will switch needinfo over to Ian for designs.
Flags: needinfo?(ibarlow)
Flags: needinfo?(deb)
This is being done in bug 704229.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: DUPLICATE → ---
Assignee: nobody → wjohnston
tracking-fennec: ? → 31+
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(ibarlow)
You need to log in before you can comment on or make changes to this bug.