The debugger on jwt.io accepts both base64 and base64url encoded tokens. However, since the standard specified base64url, it would be nice if the debugger generated an error for base64 tokens.
Thanks for the feedback, your observation is correct and that situation seems to being already tracked here. Having said that, the age of the existing report seems to indicate that it may be something that will continue like that for a while.