Turns out the fix was in the Chrome Web Store ...