Hey thanks for the heads up! This seems to be a bug with the latest version of Chrome. Until I figure it out, please try on an older version or Safari/Firefox.