Thanks for the feedback! We're looking into fixing this in one of the upcoming updates to the extension.