Thanks for sharing! The extension has been updated to v1.7.3 which fixes the mentioned issue. The related bugzilla bug is reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=1817806