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

Issue 819331 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Settings: going directly to chrome://settings/syncSetup triggers console error

Project Member Reported by scottchen@chromium.org, Mar 6 2018

Issue description

VM2252:1 Uncaught ReferenceError: cr is not defined
    at <anonymous>:1:1

Possibly in people_handler.cc a FireWebUIListener is triggered before cr is registered on the frontend side.
 

Comment 1 by aee@chromium.org, Mar 28 2018

Cc: aee@chromium.org

Comment 2 by aee@chromium.org, Apr 3 2018

@scottchen, I'm having trouble reproducing this.

Here are the steps I've tried:
1. sign in
2. navigate to chrome://settings/syncSetup
3. no error
4. close chrome
5. open it already signed in
6. navigate to chrome://settings/syncSetup

All the settings on the sync page are set to the factory defaults (sync everything).

Is there a missing step or does the prefs need to be in a specific state to reproduce this?

Comment 3 by aee@chromium.org, Apr 9 2018

Status: Unconfirmed (was: Available)

Comment 4 by aee@chromium.org, May 14 2018

Cc: -aee@chromium.org

Comment 5 by ajha@chromium.org, Jun 6 2018

Labels: Needs-Feedback
Adding Needs-Feedback as per C#2.

Sign in to add a comment