WIP: Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform

Fynbo · December 21, 2021, 2:01pm

Bricks Version: 1.3.6
Browser: Chrome 90
OS: Windows 10
URL: https://synlighed.nu/

Chrome console flag:
navigator

Related official statement:

Mainly:

To fix this issue, replace the usage of navigator.userAgent , navigator.appVersion , and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData .

Michael · December 21, 2021, 3:16pm

@Fynbo

I might not be 100% correct, but I don’t think this Bricks related and more so a chrome extension. If you hover over the onloadwff.js:1 it will give you the path of what is causing it. My feeling is that it will start with something like chrome-extension://

timmse · December 21, 2021, 5:10pm

Hi guys,

The “potential issue” occurs when using the JS Webfont Loader method. Fun fact about the Webfont loader: it was initially developed by google and typekit and last updated around about five years ago

We’ll see what we can do about it, but it isn’t as critical as you can see on the “Proposed rollout plan”.

Best regards,
timmse

Fynbo · December 22, 2021, 1:04pm

Am I right in assuming uploading the custom font directly into the builder circumvents the use of the JS Webfont Loader method? (As well as other advantages; mainly GDPR-related)

timmse · December 22, 2021, 1:29pm

I just switched to the CSS loading method, and the notice is still there (for another js script).
This means that other scripts are affected as well. But again: from my point of view, this is in no way critical or jeopardizes your GDPR compliance in any way.