UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
Run the following code:

try{
  console.log(Function('/)/') & 0);
}catch(a){
  console.log(1);
}

What is the expected behavior?
According to the spec, shouldn't this code print 1 instead of 0? In the spec in section "Early syntax errors" it says that wrong regex (in this particular case "Invalid regular expression: /)/: Unmatched ')'") should trigger an error while parsing. In Mozilla Firefox it prints 1 as expected.

What went wrong?
Chrome somehow succeeds to parse wrong regex and doesn't throw a syntax error which yields printing 0 instead of 1, which in real code may result in behavior unconsistent to the ES spec.

Did this work before? No 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 
Flash Version: Flash is disabled and btw its not relevant here