Related to the other ticket I just resolved, but it looks like
this is rendering correctly now after a cache invalidation on our
side. This is typically not needed, but sometimes the servers run
into problems. Thanks for notifying us, and sorry for the delayed
response!