Closed sankargorthi closed 9 years ago
That's a Chrome bug. We ran into it as soon as Canary became Stable. I am confident that the comments used for annotations are causing this bug in Chrome and it wasn't properly unit tested. (regression, that is)
https://code.google.com/p/chromium/issues/detail?id=451015
Removing new lines in the require implementation didn't seem to help either. Closing this as it's not component(1)'s problem.
putting debug points on the sources of home.html shows the incorrect line of code. (happens on canary as well)
Works in Firefox as the debugger doesn't show the
lines in the source.