1757521 - Tableau visualisation - Unexpected error - *** is undefined

Status: RESOLVED WORKSFORME

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[ai34w1]

Attachment: Logs of alerts/warning/errors for the page in question from Firefox, Edge, Safari and Chrome

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

Go to https://public.tableau.com/app/profile/eudemocracy/viz/Europeanparties-Donationsandcontributions2018-2020/Mappingidentifieddonations
(this applies to a number of other Tableau visualisations, but not all)

Actual results:

The visualisation displays and, a couple of seconds later, an error message appears.
It is entitled "Unexpected error" and reads "TypeError: Z[0] is undefined" (sometimes the "Z[0]" is replaced with "e.$0".

Expected results:

The same visualisation displays properly and without error messages on Chrome, Safari and Edge. Firefox is the only browser triggering an error message.
To be sure, all browsers shows warning and alerts in the console, but none create an actual error.
This is noted on Firefox 98 but also happened, in the past, with previous versions. The error also displays in troubleshooting mode, so addons are not the source.
Attached are the console logs for all four browsers.

Comment 1

[Hani Yacoub, Desktop QA]

I didn't see the same error as the one described in the bug.
The only error message displayed on Firefox and isn't displayed in other browsers is this:
The connection to https://clientstream.launchdarkly.com/eval/5fc695baacf74e09ce48a061/eyJhbm9ueW1vdXMiOnRydWUsImtleSI6InNoYXJlZCJ9 was interrupted while the page was loading.

Please try if the issue occurs in safe mode. Here is a link that can help you do that: 
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Thanks.

Comment 2

[ai34w1]

Thanks for checking, Hani! So, on both macOS and windows, merely running troubleshoot mode does not solve the issue and I still get the error message on visualisations. However, on macOS, I set up an entirely new profile (leaving it untouched, with no addons or changes) and, there, no messages appear. I guess that still rules out addons as the source of the issue.
Additionally, I should mention that I have a user.js on mac (which I believe is kept when running troubleshoot mode), but I do not have it on windows and the error persists in troubleshoot mode, so the user.js doesn't seem to be the issue either.

Comment 3

[ai34w1]

PS: to be clear, with brand new profile, it works even without troubleshoot mode (tested now both on macOS and windows).

Comment 4

[ai34w1]

Attachment: Example of error message

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 6

[Alex Cornestean]

Hello,

Since the issue appears to happen in Troubleshoot mode as well, as already mentioned throughout the report, add-ons and/or themes are not the cause of this.

As such I’ll be moving the issue to a more appropriate component. In case of error, please move the bug to the correct one. Thank you !

Comment 7

[ai34w1]

@Alex, thanks, this does seem more appropriate than WebExtensions. Happy to provide any other information that may be useful.

Comment 8

[ai34w1]

Anyone has any idea about this?

Here is what a typical error looks like (got the error straight from the Tableau Public website, to ensure that it was not linked to the embed of the Tableau visualisation on another website; in both cases, however, the error message is the same):

Uncaught TypeError: Z[0] is undefined
    $6                          https://public.tableau.com/vizql/v_202212203111040/javascripts/ViewerBootstrap.js:5
    logMetricsEvent   https://public.tableau.com/vizql/v_202212203111040/javascripts/ViewerBootstrap.js:5
    e                            https://public.tableau.com/vizql/v_202212203111040/javascripts/vqlweb.js:29
    ir                            https://public.tableau.com/vizql/v_202212203111040/javascripts/vqlweb.js:8
    wrap                      https://public.tableau.com/vizql/v_202212203111040/javascripts/vqlweb.js:10
    nrWrapper            https://public.tableau.com/views/Europeanparties-Donationsandcontributions2018-2020/Mappingidentifieddonations?:display_static_image=y&:bootstrapWhenNotified=true&:embed=true&:language=en-US&:embed=y&:showVizHome=n&:apiID=host0#navType=1&navSrc=Parse:148

[From: https://public.tableau.com/app/profile/eudemocracy/viz/Europeanparties-Donationsandcontributions2018-2020/Mappingidentifieddonations]

Comment 9

[Mark Striemer [:mstriemer]]

This doesn't seem like it's clearly a Firefox bug to me. Does it work in Private Browsing with your profile that shows the error? Perhaps a cookies issue with Tableau?

Comment 10

[ai34w1]

(In reply to Mark Striemer [:mstriemer] from comment #9)

This doesn't seem like it's clearly a Firefox bug to me. Does it work in Private Browsing with your profile that shows the error? Perhaps a cookies issue with Tableau?

No, it work neither in Private Browsing nor in troubleshoot mode. Always the same error message. Also cannot be a cookie issue as cookies and site data for Tableau are cleared on exit (but allowed otherwise).

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mossop, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 12

[ai34w1]

Not so severe in itself (all online things considered), but it really f*s up the display of the pages (by having the scroll jump up and down every time an error message is displayed) and breaks many visualisations.

Comment 13

[ai34w1]

Thanks :mossop.
Really hope this can move forward in a timely manner!

Comment 14

[u592880]

Quick update since this isn't really moving forward:

• error message appears on FF 101 on macOS;
• error message appears on FF 99 on Windows;
• error message appears on Tor Browser based on FF 91.8esr on macOS;
• error message does not appear on Safari on macOS; and
• error message does not appear on Edge on Windows.
  This therefore really seems like an issue on the FF side. Anyway this could be expedited?

Comment 15

[ai34w1]

I thinks I have narrowed this down to resist.fingerprinting. When set to true, the message appears; when set to false, it does not. Can anyone reproduce this? @Hani Yacoub?

Comment 16

[ai34w1]

If confirmed, should we then change the component?

Comment 17

[Hani Yacoub, Desktop QA]

Managed to reproduce the issue after setting "privacy.resistFingerprinting" to true on macOS 11.6, Windows 10 x64 and on Ubuntu 20.04 x64.

Comment 18

[ai34w1]

Hurray for bug reproduction (so to speak). The issue was also notified to Tableau and they opened an issue; liaising may help address this.
https://community.tableau.com/s/question/0D78b000008Y5ivCAC/detail

Comment 19

[ai34w1]

Hi @Hani Yacoub, are there any developments on this? This keeps being extremely frustrating and it would be great to address it. Since all other browser work well with Tableau, it shouldn't be so hard to address this. Would love to hear back!

Comment 20

[Hani Yacoub, Desktop QA]

I will set this bug to "Privacy: Anti-Tracking" component to gain visibility, please feel free to change the component if there is other one more accurate.
Thanks.

Comment 21

[Simon Mainey]

without deep diving, this totally smells like performance.measure, see bug 1621729 for numerous examples

Comment 22

[ai34w1]

HAppy to see this move forward. @Simon, if confirmed, would this make it easier to address?

Comment 23

[Simon Mainey]

(In reply to ai34w1 from comment #22)

HAppy to see this move forward. @Simon, if confirmed, would this make it easier to address?

bug #1621729 (or more precisely overall timing mitigations) is already on tjr's radar for some reviews/fixups/tweaks (and will be addressed in his spare free time, if possible). There is nothing we can do to speed that up, except submit patches. RFP is not front facing in Firefox - your solution (for now) is to not use it: e.g. in a secondary profile/release-channel

Comment 24

[Tom Ritter [:tjr]]

I think this has been fixed, are you able to confirm?

Comment 25

[ai34w1]

From what I can see, yes -- which is great! Any idea what this was or how it was fixed?

Comment 26

[Simon Mainey]

Any idea what this was or how it was fixed

Bug 1811567 - prior to this bug landing performance.measure would always return an empty array, which is why you got the error Z[0] is undefined. Now we record the time, but restricted it to 60FPS

Comment 27

[ai34w1]

Cool, so I have the feeling this helped - perfect and thanks for the great work!