Hi @julienallard1:
I’m trying to work a solution to keep the debugger working. Safari’s privacy mode, Brave’s core privacy features, and security changes coming down the pipeline in Chrome 80 and next release of Firefox after that will break the debugger for everyone. So we’re trying to stay ahead of the curve here.
The thing is, the change I made isn’t quite there yet.
Looking at your screenshot I think you’re on a bubble site with a custom domain, but which isn’t being served over SSL. (This is a pretty uncommon configuration.) I’m going to push a fix for this combination moving forward, but there are some other pieces I need to get in place to fully future proof the debugger.