* Feature implementation status:

Fully implemented and enabled by default on trunk. Can be disabled via a command line flag.

* Link to Design Doc:

https://docs.google.com/document/d/1walNnk_COIcIbBByb8KG0vqXXdhsY8Ax7v921oGKhNA/edit

* Link to Test Plan:

https://docs.google.com/document/d/1walNnk_COIcIbBByb8KG0vqXXdhsY8Ax7v921oGKhNA/edit#heading=h.nk8ivvsmdrin

* Link to demos (if any):

https://mounirlamouri.github.io/sandbox/media-focus.html

* What's automated? (Unit tests, API tests, Browser tests)

Unit tests:
 - media/blink/webmediaplayer_impl_unittest.cc

Browser tests:
 - content/renderer/media/renderer_webmediaplayer_delegate_browsertest.cc
 - content/browser/media/session/media_session_visibility_browsertest.cc

* Is there a mechanism to turn off the feature if it breaks product functionality or performance?

It is behind a flag. The flag will be linked to a Finch experiment.

* List UMA stats if any:

https://docs.google.com/document/d/1walNnk_COIcIbBByb8KG0vqXXdhsY8Ax7v921oGKhNA/edit#heading=h.pb8zee5yg6ov

* Any performance impact?

Nothing unexpected. If the user is playing a video in the background, there will be performance impact because of the playback. Less than playing video is the foreground and a bit more than playing audio in the background.

* Are there any special points of interest from a testing perspective?

Nothing specific.

* What is the crbug label for the feature?

N/A

* Are there any other team members or mailing lists that should be notified if issues are found?

avayvod@ and mlamouri@
Team: chrome-media-lon@