Create a support article around plausible browser privacy extension issues + consider new embed code?

[mattheworiordan]

A customer reported the following issue:

In the chrome browser - I see this: ably.min-1.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT (index):207 Uncaught ReferenceError: Ably is not defined

This turned out to be a browser extension https://www.eff.org/privacybadger blocking the loading of the Ably JS from our CDN, and indeed access to any of our domains.

Trying this locally, I could not get the same result:

However, the extension can "learn" which domains to block, and is also configurable.

As a result, should we:

• [ ] Perhaps recommend a different embed code, so instead of <script lang="text/javascript" src="https://cdn.ably.io/lib/ably.min-1.js"></script>, perhaps something like

<script lang="text/javascript" src="https://cdn.ably.io/lib/ably.min-1.js"></script>
<script type="text/javascript">if(!Ably) { console.error('Ably is not loaded. See https://help.ably.io/error/XXXX for help'); }</script>

It's more verbose sure, but only one line and could help users understand the issues.

• [ ] Create a support article.

cc @SimonWoolf @paddybyers @tomczoink

┆Issue is synchronized with this Jira Task by Unito