@sgunhouse This is really a bad move IMO. And don't you hate when a browser upgrade make you go to the forum to look for a button that was always there because it has been replaced by a far slower, almost useless one?

Constructive idea: Next time instead of replacing it, just add the new one with a notification pill explaining what's going on and providing the direct configuration link.
Thanks

@lavanyadeepak-0
Same issue. Shouldn't browser.js also not emit such messages in the DOM at least

@sgunhouse This is really a bad move IMO. And don't you hate when a browser upgrade make you go to the forum to look for a button that was always there because it has been replaced by a far slower, almost useless one?

Constructive idea: Next time instead of replacing it, just add the new one with a notification pill explaining what's going on and providing the direct configuration link.
Thanks