Actually it looks like this was fixed in a rollout on the 4th. I wasn't seeing that update when I looked yesterday, but it's working now. :)