New issue
Advanced search Search tips

Issue 620507 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

touch top-right of touch screen will max volume and blast ears

Project Member Reported by chaok@google.com, Jun 15 2016

Issue description

Mode: force_next
Version: 52.0.2743.32
Reproduction Steps: 
1. On Pixel 2 with touch screen
2. touch top-right

Observed:
Volume maxes to 100% with no confirmation and ears are blasted
I nearly jumped out of my seat when this occurred. 

Expected:
warning dialog similar to that of on ANdroid that warns about using loud audio above a certain threshold that requires an explicit agree/ok button in a dialog.

 
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 16 2016

Labels: Hotlist-Google
Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)
Labels: Phase3
Owner: dmazz...@chromium.org
Oh man, yes... I can see how this is an issue... but really, I am not sure that this is a CVox issue. Pixel has a touch-sensitive area at the right of the screen that controls volume. Unless CVox just ignores this, I am thinking that volume warning levels ought to be taken up by the audio team... I.E I don't think that this is only specific to CVox.
Re #4: the volume feature is a part of ChromeVox and works on all touchscreen devices, not just the Pixel.

Perhaps if the scrolling was made to be relative to the current volume, regardless of where the touch starts?

Comment 6 by dtseng@chromium.org, Oct 29 2016

Labels: -Phase3 phase4
Owner: ----
Status: Available (was: Assigned)
Labels: NewComponent-Accessibility-ChromeVox NewComponent-Accessibility
Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox
Components: -UI>Accessibility
Project Member

Comment 11 by sheriffbot@chromium.org, Apr 23 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
Status: WontFix (was: Untriaged)
Agreed with the comment in #4, so going to close out this specific issue for now. 

Sign in to add a comment