Resolved in bug-fix for a previous issue apparently. Quoting Theresa Henze (from PNU):
I can't seem to reproduce the problem. [...] However, I fixed #15 and maybe this is no longer an issue. [...] I just released version 1.2.1. Could you please check whether your problem still occurs in the updated version?
Tested with newly released plugin version 1.2.1 and it works. Closed the issue, thanks to Charleso for pointing me in the right direction!