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

Issue 629356 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Volume keys behave oddly on panther when only DisplayPort is connected

Project Member Reported by derat@chromium.org, Jul 19 2016

Issue description

Version 51.0.2704.106 (64-bit)
Platform 8172.62.0 (Official Build) stable-channel panther
Firmware Google_Panther.4920.24.26

I'm seeing strange volume key behavior on this device (which I hadn't used in a while).

I'm using an HP KU-1156 USB keyboard (which was the default from the Techstop in SF). At chrome://settings-frame/keyboard-overlay, I have "Treat top-row keys as function keys" unchecked, i.e. the top-row keys should act as system keys instead.

When I press F10 (which is usually "Volume Up"), the volume slider appears and is unmuted, but the volume doesn't increase no matter how many times I press it. Pressing either F8 (Mute) or F9 (Volume Down) appears to mute the volume -- the slider appears and is grayed out.

After the slider appears, I'm able to drag the level up using the mouse to unmute, but the keys still behave incorrectly: F10 doesn't do anything, and F8 and F9 both mute.

To summarize:
When muted: F8 and F9 do nothing, F10 unmutes but doesn't change level
When unmuted: F8 and F9 mute without changing level, F10 does nothing

I have an HP Z24i display connected via DisplayPort (and no headphones currently connected) -- could that be confusing things? I filed a feedback report at https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReport=12332284536.
 

Comment 1 by derat@chromium.org, Jul 19 2016

Cc: abodenha@chromium.org
Components: UI>Shell>StatusArea
Summary: Volume keys behave oddly on panther when only DisplayPort is connected (was: Volume keys not working correctly on panther)
The keys behave normally after I connect headphones via the 3.5 mm audio jack and use them as the output device, so the issue here may just be that the UI doesn't do a good job of communicating to the user that there aren't any audio devices. Maybe we should display a notification when the volume keys are pressed in this state.
Owner: jen...@chromium.org
Status: Assigned (was: Untriaged)
Cc: tdander...@chromium.org
Labels: M-54
Could this be fixed as we update the audio row for MD System Menu?
If we're showing a notification as suggested in #1 (presumably in the notifications center) then this can be addressed independently of the MD work since the system menu itself won't be changing appearance.

Comment 5 by jen...@chromium.org, Jul 28 2016

How about we show a muted volume icon and do not pop up volume bar if there is no audio output? Or we can use an volume icon like muted one, but a different color looking like disable?

Comment 6 by derat@chromium.org, Jul 28 2016

Hmm. I think it may still be a good idea to display some sort of visual feedback when the user hits the keys so they know that they're not having function vs. system key issues or running into a bug. (I was confused because stumpy had an internal speaker, IIRC, and I didn't realize that panther didn't have one.) Maybe we could display a different icon in the bubble to indicate that there's no output device connected?

Comment 7 by jen...@chromium.org, Jul 28 2016

#6, a different icon in the bubble might be good visual cue. We need to PM in this thread. 
Cc: kuscher@chromium.org
kuscher@ who would be good to own volume bubble from the PM side?
Status: Archived (was: Assigned)

Comment 10 by ketakid@google.com, Mar 18 2017

Labels: Pri-3
Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.
Project Member

Comment 11 by sheriffbot@chromium.org, Apr 12 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 12 by derat@chromium.org, Apr 12 2018

Owner: zalcorn@chromium.org
Over to Zach.
Owner: ovanieva@chromium.org
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: WontFix (was: Assigned)
Haven't heard about this in the long time, and I was the reporter. Please reopen if it's still an issue.

Sign in to add a comment