Hi, thank you for reporting this issue. You’re right – the extension wasn’t working as expected. A fix has been applied in version 1.2.1, please give it another try!