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

Issue 775974 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Support new method to get device uid from PPB_DeviceRef_Dev interface

Project Member Reported by xzh...@adobe.com, Oct 18 2017

Issue description

Chrome Version: 61.0.3163.100 (Official Build) (64-bit) (cohort: Stable)
OS: Win/Mac/Linux

What steps will reproduce the problem?
When same audio devices are plugged into the system, client will see same device names. When device change happens, for example, one of the devices are removed/added, client is not able identify which device is actually changed, so it cannot make the right decision to switch audio playback to the appropriate device.

What is the expected result?
PPB_DeviceRef_Shared has the ability to return device uid stored in |DeviceRefData::id|, so we only need to add a new method
|PPB_DeviceRef_Dev::GetId()|, and implement it through |PPB_DeviceRef_Shared::GetId()|-> |DeviceRefData::id|

What happens instead?
When same output devices are connected to the system, switching audio output among those devices will be messed up.

 
Status: WontFix (was: Untriaged)
Thanks for filing this issue.  As we discussed earlier this year, PPAPI has been frozen, so absent very significant/ critical business drivers we're explicitly not making changes.

While I appreciate the use case as described, the pattern requires an explicit user behavior and is relatively easy to work through.

Sign in to add a comment