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

Issue 794436 link

Starred by 1 user
Status: WontFix
Owner:
ew...@chromium.org
Closed: Dec 2017
Cc:
gov...@chromium.org
nyerramilli@chromium.org
pbomm...@chromium.org
msarda@chromium.org
rbasuvula@chromium.org
█ bauerb@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression:Chrome help page doesn't open after tap/touch on 'sign into Chrome' link button.

Reported by vku...@etouch.net, Dec 13 2017 
Chrome Version:65.0.3292.0 (Official Build)Revision	7d40cf8237fbf29b3dffb6dca3376c10c3df176b-refs/heads/master@{#523290}(32/64 bit)
OS:Windows 10 Touch device

What steps will reproduce the problem?
(1)Launch chrome and Tap on avatar icon > manage people > add person 
(2)Tap on checkbox of 'supervised this person...'
(3)Now tap on 'sign into Chrome' link button and observe

Actual: Chrome help page doesn't open after tap/touch on 'sign into Chrome' link button.

Expected: Chrome help page should open after tap/touch on 'sign into Chrome' link button.

This is a Windows 10 touch device specific regression issue broken in 'M63' and
below is manual regression range
Good Build: 63.0.3213.0 
Bad Build:  63.0.3214.0
Actual_signin.mp4
333 KB View Download

Comment 1 by vku...@etouch.net, Dec 13 2017

Labels: hasbisect-per-revision
Owner: bauerb@chromium.org
Status: Assigned (was: Unconfirmed)
You are probably looking for a change made after 501240 (known good), but no later than 501241 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/a00d6fa0a60f520958721cf380dedfe7981e353c..2a117c0410ece4e30c8ccc4cd00d62af24557ec1

Suspect : https://chromium.googlesource.com/chromium/src/+/2a117c0410ece4e30c8ccc4cd00d62af24557ec1
Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Comment 2 by msrchandra@chromium.org, Dec 13 2017

Cc: pbomm...@chromium.org gov...@chromium.org
Labels: -M-65 M-63
@govind/pbommana -- As this issue is broken in M63, could this be considered as Stable blocker for M63. Request you to please take a look.

Comment 3 by treib@chromium.org, Dec 13 2017

Cc: bauerb@chromium.org
Components: UI>SignIn
Owner: msarda@chromium.org
That CL (re)enabled the creation of supervised users, so it made the problem visible, but it's not actually the root cause. Over to the signin team for triage - I don't know who works on the user manager these days.

Comment 4 by msarda@chromium.org, Dec 14 2017

Cc: msarda@chromium.org
Owner: ew...@chromium.org
Eli: I remember you said that the supervised users are deprecated. If they are, then maybe we do not need to worry about this bug. Otherwise, I'll take a look - so please re-assign this bug back to me.

Comment 5 by ew...@chromium.org, Dec 15 2017

Labels: -Pri-1 Pri-3
Status: WontFix (was: Assigned)
Supervised users are indeed on the path to deprecation (see Issue 736035). Given how low-priority of a bug this is, and the fact that supervised users will be deprecated once Unicorn accounts are ready for CrOS, I'm inclined to just mark it as WontFix.
►

Sign in to add a comment