Same behavior in Chrome 46 so it seems to be a Chromium issue.