Atlaskit Renderer component broken in Chrome 83 if Confluence is opened in incognito mode


Looks like recent Chrome privacy improvements made in version 83 cause Atlaskit Renderer component to throw unhandled JS exception (that breaks UI of entire page) if opened in incognito mode. Workaround is to enable 3rd party cookies (by clicking on new ‘eye’ icon). Below is the top of stack trace from Chrome Dev tools.

Uncaught DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document.
    at http://localhost:3000/static/js/bundle.js:102930:54
    at Module../node_modules/@atlaskit/emoji/dist/esm/api/internal/UsageFrequencyTracker.js 
at Module../node_modules/@atlaskit/renderer/dist/esm/ui/ExtensionRenderer.js (http://localhost:3000/static/js/bundle.js:145071:81)

I thought I’ll report it as a post on Community so other app developers are also aware of this problem (please let me know if there’s more appropriate place to report such issues)

1 Like

I’ve let the responsible team know—expect more soon :slight_smile:

1 Like

Hi @LukaszWiatrak,

I’m a developer on the editor platform team and I’m looking into this issue. I’m not yet able to reproduce this issue in the renderer locally, or in Jira or Confluence in Chrome 85 Canary (Incognito) unless I block all cookies.

Could you share some more information on how to reproduce the issue? Are you able to reproduce in the renderer on the examples?

Thanks very much for reporting this :slight_smile:

Could this be related to the new fancy privacy api coming in safari, chrome and Firefox (each one has a different implemention)?

Did you test in a connect app on a different domain?

1 Like

I’ve checked behavior on deployed production version of application and fortunately it’s working fine. So it looks like this problem is limited only to my local environment setup in which I’m fetching front-end assets from different URL (localhost with different port - webpack dev server) than the app itself - which is probably causing problems.

Sorry for prematurely raising an alarm for a issue that has much more limited impact than from what it looked like on first sight.

Yep okay, that’s good to hear.

No worries, please reach out if you find future problems :slight_smile:

I got this error too with the ‘navigation next’ component. The component has trouble accessing the localStorage when third party cookies are blocked. Either by using the incognito mode or by explicitly prohibiting it in the chrome settings.

It can be reproduced easily with accessing this example with Chrome in incognito mode:

Chrome Version: 83.0.4103.116