The comment by ZachS pointed this out and a fix has been deployed. It should be working now. Please let me know if it's not.