If it’s the case normally with the next version of the browser extension (v4.0.0) it should be fixed.
The extension for Google Chrome is already available in a BETA version btw. If you want to take a look how to use it if you wish you can find a quick procedure here:
