New issue
Advanced search Search tips

Issue 673901 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
Team-Accessibility



Sign in to add a comment

Set key repeat rate based on selected user pod in start screen

Project Member Reported by abodenha@chromium.org, Dec 13 2016

Issue description

If a user sets a key repeat rate (possibly for a11y reasons) we should honor that when a user's pod is selected.

Ideally, we'd honor other things as well like mouse accel, cursor-size, etc. but those might be jarring while switching pods.

steel@ & alemate@ curious about your thoughts on difficulty. Is this something a noogler could take on?

zalcorn@ & lpalmaro@ thoughts on this? Does it sound reasonable? Do you think we should do full launch review for such a change or is a feature bug sufficient.
 
This sounds reasonable to me, and would fit nicely with crbug/651905 if we wanted to combine them as a single launch bug.
Cc: michae...@chromium.org
We do apply the owner's settings to non-signed-in sessions (like the sign-in screen) for:

* UI language (locale)
* Swapping right/left mouse button
* Enabling touchpad tap-to-click
* Time zone settings
* Virtual keyboard (maybe?)

So we could expand this to other accessibility settings.

This would be easier than trying to load per-user preferences when selecting a user pod, but it doesn't address having multiple users with different accessibility settings.
We also activate per-user-POD input method on focus.
So setting keyboard rate seems also reasonable.

I don't think that applying "Swapping right/left mouse button" or "Enabling touchpad tap-to-click", or "Time zone settings" or "Virtual keyboard" should be set per-user-POD, because mouse settings do not have visible feedback, so it might be very confusing if user activates POD with weird settings and then tries to click on status area, or whatever.

We also cannot apply locale settings per-user-POD, because changing locale is very long and resource-consuming operation.

Comment 4 by zork@chromium.org, Feb 8 2017

Owner: x...@chromium.org

Comment 6 by x...@chromium.org, Feb 21 2017

Status: Fixed (was: Assigned)

Comment 7 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 8 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59
Status: Verified (was: Fixed)

Sign in to add a comment