There’s been an issue plaguing me for the last week or two where chrome refuses to load and run less.js and .less files, but yet works just fine in Firefox or IE.
Here’s what I found: Turns out this the problem is caused by a security feature in chrome that disables any script that loads from
file:///[path to script] from running. If you edit the shortcut for chrome and add this switch on the end:
-allow-file-access-from-files Chrome will load and run your local scripts when it’s launched from this shortcut. It fixes the less.js problem and makes it actually usable for testing and debugging local sites.