Thanks @kazue.sasatani for surfacing and @dguzzo for adding to this thread with a workaround in the meantime! Our eng team has merged a fix for this that has not yet been released, we'll keep you updated here once that's fully deployed 
2 Likes