New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 707101 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ zqzh...@chromium.org
mlamouri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

MediaSession API and the default MediaSession should control media elements the same way

Project Member Reported by avayvod@chromium.org, Mar 31 2017 
They currently use two separate path, the API uses the existing HTMLMediaElement APIs with the user gesture flag set while the default behavior uses the delegate. This was one of the reasons leading to  Issue 689637  and thus to the  Issue 703105 .

Filing this one for tracking of the work that should reduce the scope of test coverage needed for various media related behaviors.
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 2 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by kariahda@chromium.org, May 21 2018 

Bulk edit**

This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all.

We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you.
►

Sign in to add a comment