this was a behaviour in other browsers a long time before Chrome started...