yes and no - there have always been cases like this depending on the security setting of the default browsers.
It has to do with the fact that MV uses webtechnologies on local files, which might be mistaken for a virus on a website trying to infect a computer - and something that can be blocked by browser settings if they're set to one of the higher security settings.
The fact that it works in Firefox shows that the problem is not in the project (could have been damaged files instead for example or a few other possibilities).
So now you can use that as an emergency workaround and know that the project has no bug, until the real cause is solved - which was most probably an update to the browser triggered there.
Sorry, I can't help you further on that search.