We are having the exact same issue on our side. Is this a new standard, or is it a UI bug?