I've actually found a fix for this issue, and it's not roll20 related, but I'll post it here in case anyone is experiencing this: This bug happens if you have privacy.resistFingerprinting enabled. To fix it, you can temporarily set privacy.resistFingerprinting.autoDeclineNoUserInputCanvasPrompts to false, so that next time you visit roll20 (and have a token with a tint show up) you can authorize the site to use canvas data, which will fix it. You can then set it back to true. Not sure how to mark this as solved.