Third-Party Service Worker Registration and Brave

[jonathansampson]

Describe the bug
For a user running Brave under normal settings, the service worker registration for stackblitz.io fails, as it is a third party domain. This failure prevents the localhost server from being stood up for the user's blitz. To remedy the issue, a user can modify their shields (via the lion icon to the right of the address bar) in Brave to permit third-party cookies (this setting also controls third-party service workers).

Link to the blitz that caused the error

To Reproduce
Steps to reproduce the behavior:

1. In Brave, visit https://stackblitz.com/edit/web-platform-kaxdum

Expected behavior

The "localhost" connection is established, and the content is shown.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Brave
• Version: 1.24.85

Additional context

If you catch the registration failure, you can inform the user that their security settings may have prevented the feature from working. For Brave users (there are over 30 million monthly active users at the time of this writing), you can can inform them that relaxing the shield settings for cookies (and other third-party storage) will resolve the issue. This is what I did in the GIF above. Brave can be detected via its navigator.brave.isBrave function (which returns a promise).

[SamVerschueren]

Thanks for reporting this. It's a very good point and we should definitely work on improving the experience for Brave users. I'm looping it back to the team.

[fvsch]

@jonathansampson We now have a warning component shown in Brave when the Service Worker registration fails, linking to https://github.com/stackblitz/webcontainer-core/blob/main/browsers/brave/brave.md

It actually shipped in July, but I forgot to update this issue!