@googlechrome I think we have a problem here. #bug?