Why do I have access to the new editor in Safari but when I use Brave it is the older editor? This is very confusing. 
1 Like
that’s normal and it’s not something you’re doing wrong. bubble is rolling out the new editor gradually and access is tied to the browser/session, not the account itself. so you can end up seeing the new editor in one browser and the old one in another.
brave also blocks or isolates certain cookies and experiments by default, which often keeps it on the older editor. if you disable shields for bubble.io or open the editor in a private window, it sometimes switches. otherwise, it’ll update on its own once bubble finishes the rollout.
I thought it was user specific, never would have thought it would be browser/session specific. That is so weird. Doesn’t make sense to me at all.
yeah, it feels weird at first, but it actually lines up with how they’re testing it. bubble’s treating the new editor as an experiment, so they’re rolling it out per browser/session to limit blast radius and compare behavior side by side. it lets them catch issues without breaking everyone’s workflow at once.
once the rollout is complete, it’ll be user-wide and consistent everywhere. right now it’s just an awkward in-between phase.
That’s sohnds like rubbish and im pretty sure not true. What makes you think that thats the case??
@code-escapee Do you have another explanation? I was thinking maybe if I delete the cookies in my browser, then maybe it will update.
So to fix it, I just disabled the shields and then enabled them again. Then it came through. 
1 Like
Deleting the cookies didn’t solve it?
I didn’t even try it, the toggle for disabling the shields was easier to do. It probably would have worked to delete the cookies as well.
Extensions that block ADs will block the new editor.
Brave has a native one just turn it off for bubble domain
1 Like
@J805 what rafael said. It’s about Brave blocking ads/similar. Brave is not allowing bubble to tell your editor that you are in the experimental beta version of the PE.
Yes it would be very strange for it to be based on session so seemed to be a browser distinction… thanks for clarifying
I’m using Zen browser sometimes these days (which is based on mozilla), and the new editor just doesn’t seem to be enabled on non-chrome browsers. Somewhat annoying…