That was a bug in Chrome (http://crbug.com/361587), it's not inherent to the technology. VS Code ended up implementing the logic in JS to work around it.