Thanks for letting us know, this is a known issue with this version of our Firefox addon.
It will be addressed in the next version.