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

Issue 786727 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 784047


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Input method list should be expanded when Settings is launched from input method shelf menu

Project Member Reported by michae...@chromium.org, Nov 18 2017

Issue description

Chrome OS has a setting that adds an item to the shelf for input methods. Clicking this button opens a menu that lets you switch between input methods.

The menu has a cogwheel that opens chrome://settings/languages, which launches Settings and scrolls to the "Languages and input" section. But the "Input methods" list is not expanded, so to actually change input method settings, you have to toggle that list.

This means that opening the extension settings page for a particular input method (e.g., to enable auto-correct; see issue 784047#4) requires 4 clicks:

With the option to show input method settings in the shelf enabled:
1. Click the input method settings button in the shelf
2. Click the cogwheel in the menu
3. In Settings, click the input methods list
4. Click the "open in new tab" button next to the desired input method

Maybe we should auto-open the input methods list in Settings when we launch from the input method shelf menu.

Although it could be argued that the user may want to use a different part of language settings (you have to add a language before you can add its input methods, for example), so maybe we shouldn't do this....
 
Blocking: 784047

Comment 2 by vadimt@chromium.org, Nov 27 2017

Labels: Not-Touch-Friendly-Launcher
Labels: MD-Settings-Languages
Labels: -MD-Settings-Languages Hotlist-MD-Settings-Languages
Owner: manucornet@chromium.org
Components: -UI>Shell>Shelf UI>Shell>StatusArea
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment