CustomTab: media notification not displayed

NEW
Assigned to

Status

()

P3
normal
2 years ago
a year ago

People

(Reporter: sorina, Assigned: esawin)

Tracking

(Blocks: 2 bugs)

57 Branch
ARM
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox57 wontfix, firefox58 wontfix, firefox59 affected, firefox60 affected)

Details

(Reporter)

Description

2 years ago
Environment: 
Device: Huawei Honor (Android 5.1.1), Asus ZenPad 8 (Android 6.0.1);
Build: Nightly 57.0a1 (2017-08-30);
Prerequisite: Custom tabs are enabled in settings.

Steps to reproduce:
1. Launch CustomTab activity playing a video (e.g. youtube.com, reactforbeginners.com).
2. Swipe down device notification area.

Expected result:
A media control notification is displayed: a play/pause button, the page title, URL, favicon.

Actual result:
The media notification is not displayed.
Eugen can we get this hooked up? I think for now don't worry about exposing anything in GV, though we probably want to do it that way eventually. Just use whatever we need from Fennec.
Assignee: nobody → esawin
Priority: -- → P2
Jack/Tori, can you look at this and see if it makes sense from UX perspective to show media notification in custom tabs?
Flags: needinfo?(tchen)
Flags: needinfo?(jalin)
Agree with Sorina's expectation. When media is playing in custom tabs, we show media control notification. The behavior is the same as in Fennec.

For UX perspective, a media is playing in the custom tab and users press home key to let the media playing in the background, so if users want to pause the media, they just easily swipe down the device notification then pause the media. (They don't need to find the browser in the task manager, and find the media on the webpage, and then pause the media...hard to find)
Flags: needinfo?(jalin)

Updated

2 years ago
Flags: needinfo?(tchen)

Comment 4

2 years ago
Also an issue for web apps. I suppose we can we use this same bug for that?

Updated

2 years ago
status-firefox58: --- → affected

Updated

2 years ago
Blocks: 1212648
(Assignee)

Comment 5

2 years ago
(In reply to Oana Horvath from comment #4)
> Also an issue for web apps. I suppose we can we use this same bug for that?

Yes, I'll address both, custom tabs and PWAs, in this bug.
status-firefox57: affected → wontfix
status-firefox58: affected → wontfix
(Reporter)

Updated

a year ago
status-firefox59: --- → affected
[triage] Bulk edit from title: this is a non-critical issue. Please remove priority if you wish this to be re-triaged.
Priority: P2 → P3
(Reporter)

Updated

a year ago
status-firefox60: --- → affected
You need to log in before you can comment on or make changes to this bug.