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

Issue 875108 link

Starred by 1 user
Status: Fixed
Owner:
zork@chromium.org
Closed: Sep 10
Cc:
adlr@chromium.org
█ kbleicher@chromium.org
michae...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Touch-to-click can end up in the wrong state if multi-users and they don't have the same touch-to-click settings

Project Member Reported by diand...@chromium.org, Aug 16 
Chrome Version: 69.0.3497.35 beta
OS: Chrome OS

See feedback report <https://listnr.corp.google.com/product/208/report/85605571234?dateRange=All>

---

From that report:

With the most recent update touch-to-click sees a new issue:

Setup:
- account1: regular click
- account2: touch to click

Issue:
After every reboot touch-to-click is disabled on the login screen (expected). When account2 logs in, touch to click stays disabled but the settings ui still shows it as enabled. Only by disabling and re-enabling touch to click does account2 get this feature after login.

Partial resolve:
When I enable touch-to-click on account1 as well so that both have it, the issue goes away and touch-to-click is active even on the login screen.
Disabling touch to click again for account1 reintroduces the issue for account2.


The issue seems to have been introduced with the most recent update from this week and I already discussed a bit with @dianders about it today.

Comment 1 by cindyb@chromium.org, Aug 31 

Hi, please provide the latest status of this issue.

Comment 2 by dgagnon@chromium.org, Sep 4

Cc: kbleicher@chromium.org
kbleicher@ is this the same issue you were having?

Comment 3 by kbleicher@google.com, Sep 5 

No, the issue I saw was crbug/872786:

- Indicator displayed tap-to-click is disabled
- Feature was actually on, however

To Mitigate
- Have to turn the feature on and back off to really turn it off

Comment 4 by michae...@chromium.org, Sep 5 

This does sound the same as  issue 87278 . We've merged fixes into M70 and M69.

Comment 5 by michae...@chromium.org, Sep 5

Cc: adlr@chromium.org
Owner: michae...@chromium.org
Status: Started (was: Untriaged)
to me to verify the same merges fix this issue

Comment 6 by cindyb@chromium.org, Sep 7 

Hi michaelpg@, were you able to verify the merge fixed the isue?

Comment 7 by cindyb@chromium.org, Sep 10

Cc: michae...@chromium.org
Owner: zork@chromium.org
michaelpg@ is OOO. zork@ will validate.

Comment 8 by michae...@chromium.org, Sep 10 

I'm 95% sure this issue is fixed on the branch but I haven't actually tested it on the latest 69 image yet. However I'll be able to check later tonight when I stop by the office.

Comment 9 by zork@chromium.org, Sep 10 

This appears to be fixed on 69.0.3497.87.  I tested with two users, one with Tap to click enabled, one with it disabled.  After reboot, tap to click works on the login screen, and the setting is properly reflected for each user upon login, both in behavior and on the settings page.

Comment 10 by cindyb@chromium.org, Sep 10

Status: Fixed (was: Started)
Great! Marking the bug fixed and closing. Thanks!
Project Member

Comment 11 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Sep 10

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-69; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-69 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 12 by sheriffbot@chromium.org, Oct 23

Labels: -Merge-TBD
►

Sign in to add a comment