Bug 1557153 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

A couple of notes to help debug here:

- `Mozilla.Client.FirefoxDetails` is a bedrock wrapper around the UITour API. Returning `accurate: false` indicates that UITour is not enabled for a user. However, to test if this is a problem with UITour, or a problem in bedrock, it may be better to suggest another snippet of code that is a little "closer to the metal":

1. Open https://www.mozilla.org/en-US/firefox/63.0/tracking-protection/start/?variation=0&step=1
2. Open the Web Console
3. Paste the following code and obeserve the response:

```
Mozilla.UITour.getConfiguration('sync', function (config) {
    console.log(config);
});
```

It's also worth noting that a user should only see a tour at the /tracking-protection/ URL if they have TP enabled. People only get sent to this page once a tracker is detected, and the tour relies on the TP feature being active in order to work.

The result of the console.log should return a users signed-in state for Sync. If UITour is not working, there may be no output returned at all.
A couple of notes to help debug here:

- `Mozilla.Client.FirefoxDetails` is a bedrock wrapper around the UITour API. Returning `accurate: false` indicates that UITour is not enabled for a user. However, to test if this is a problem with UITour, or a problem in bedrock, it may be better to suggest another snippet of code that is a little "closer to the metal":

1. Open https://www.mozilla.org/en-US/firefox/63.0/tracking-protection/start/?variation=0&step=1
2. Open the Web Console
3. Paste the following code and obeserve the response:

```
Mozilla.UITour.getConfiguration('sync', function (config) {
    console.log(config);
});
```

The result of the console.log should return a users signed-in state for Sync. If UITour is not working, there may be no output returned at all.

It's also worth noting that a user should only see a tour at the /tracking-protection/ URL if they have TP enabled. People only get sent to this page once a tracker is detected, and the tour relies on the TP feature being active in order to work.
A couple of notes to help debug here:

- `Mozilla.Client.FirefoxDetails` is a bedrock wrapper around the UITour API. Returning `accurate: false` indicates that UITour is not enabled for a user. However, to test if this is a problem with UITour, or a problem in bedrock, it may be better to suggest another snippet of code that is a little "closer to the metal":

1. Open https://www.mozilla.org/en-US/firefox/63.0/tracking-protection/start/?variation=0&step=1
2. Open the Web Console
3. Paste the following code and obeserve the response:

```
Mozilla.UITour.getConfiguration('sync', function (config) {
    console.log(config);
});
```

The result of the console.log should return a users signed-in state for Sync. If UITour is not working, there may be no output returned at all.

- It's also worth noting that a user should only see a tour at the /tracking-protection/ URL if they have TP enabled. People only get sent to this page once a tracker is detected, and the tour relies on the TP feature being active in order to work.
A couple of notes to help debug here:

- `Mozilla.Client.FirefoxDetails` is a bedrock wrapper around the UITour API. Returning `accurate: false` indicates that UITour is not enabled for a user. However, to test if this is a problem with UITour, or a problem in bedrock, it may be better to suggest another snippet of code that is a little "closer to the metal":

  1. Open https://www.mozilla.org/en-US/firefox/63.0/tracking-protection/start/?variation=0&step=1
  2. Open the Web Console
  3. Paste the following code and obeserve the response:

  ```
  Mozilla.UITour.getConfiguration('sync', function (config) {
      console.log(config);
  });
  ```
  The result of the console.log should return a users signed-in state for Sync. If UITour is not working, there may be no output returned at all.

- It's also worth noting that a user should only see a tour at the /tracking-protection/ URL if they have TP enabled. People only get sent to this page once a tracker is detected, and the tour relies on the TP feature being active in order to work.

Back to Bug 1557153 Comment 3