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

Issue 696269 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Accessibility

Blocking:
issue 697691



Sign in to add a comment

[A11y Assessment - Tab strip] Context menu for tabstrip and a tab cannot be opened with keyboard navigation

Project Member Reported by hwi@chromium.org, Feb 26 2017

Issue description

Chrome Version:  56.0.2924.87
OS: Mac

What steps will reproduce the problem?
(1) Mac > Preferences > Keyboard > Shortcuts > Full keyboard access > All controls ON
(2) Cmd+L, and Shift+Tab to a tab on Tabstrip
(3) Try to open the context menu e.g. to pin or mute a tab

What is the expected result?
Be able to open the context menu

What happens instead?
Keyboard gesture unavailable

 
Blocking: 697691
Status: Available (was: Untriaged)
Labels: NewComponent-Accessibility-Browser
Labels: OS-Chrome OS-Windows
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/36389d38b27507d25f4c3f2edc66933b5a96b262

commit 36389d38b27507d25f4c3f2edc66933b5a96b262
Author: ellyjones <ellyjones@chromium.org>
Date: Mon Mar 13 20:55:49 2017

cocoa: add experimental tabstrip keyboard focus support

This change:
1) Adds a feature named TabStripKeyboardFocus,
2) Adds a corresponding flag in chrome://flags,
3) Adds support for tabs to become first responders,
4) Adds support for tabs to draw focus rings,
5) Adds support for pressing Enter on a focused tab to switch to it

BUG= 696269 

Review-Url: https://codereview.chromium.org/2743993003
Cr-Commit-Position: refs/heads/master@{#456476}

[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/app/generated_resources.grd
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/browser/about_flags.cc
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/browser/ui/cocoa/tabs/tab_controller.mm
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/browser/ui/cocoa/tabs/tab_view.mm
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/common/chrome_features.cc
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/chrome/common/chrome_features.h
[modify] https://crrev.com/36389d38b27507d25f4c3f2edc66933b5a96b262/tools/metrics/histograms/histograms.xml

Labels: NewComponent-Accessibility
Labels: -newcomponent-accessibility-browser -newcomponent-accessibility
tapted@ friendly ping - where does this stand? 
Status: WontFix (was: Available)
This one is probably WontFix now - we promoted all the tab context menu options into the Window menu, so they're now always useable. This is more Mac-ish than having a way to open a context menu I think.

Sign in to add a comment