>>No.
>>Re: the first one :
>>How are you generating source maps? AFAIR, .NET uses the //# syntax anyway. Are you minifying ? IAC, look at whatever is generating the maps - that comment would be added by the generator.
>>Re: the second one:
>>Just search in files for occurrences of 'getPreventDefault'
>>
>>>In Google Chrome the error normally points to a particular line of code which makes it easier to debug. I am not yet sure how to debug the problems in FireFox Developer's tools, they don't open the code on the line of error.
>>
>>You'd probably find the same stack trace in Chrome - it's deep within the angular handlers.
>>
>>>Attached please find a screenshot of another error - I am not sure how to debug this one. I put the break point in the first line of code in AccountController.js as well as API controller's first method - but the error seems to happen earlier.
>>
>>So does it break in AccountController? If it's undefined then it's unlikely. If it does break then it sounds as if you are intitially trying to use it before it's loaded.
>>
>>>On our daily meeting we decided the issue is most likely with the very latest FireFox itself as many other sites are not responsive in that browser now either.
>>
>>I just updated from 32.0.3 to 33.0.2 - I'll let you know whether I find any problems.....
>
>Took me a while to find out the FireFox version I am using - I have 33.0.2 as well.
>
>For now I decided to work on re-writing my user story I completed last sprint into server side paging and ui-grid instead of ng-grid. That will be quite a challenge...

And you think that will resolve the 'AccountController undefined' issue ?

FWIW I'm seeing odd behaviour with 'Select' elements when using 33.0.2 :

It appears sluggish and clicking often doesn't open the drop-down unless I hold and drag downwards. Also the first click away from the dropdown doesn't close it - a second click seems to be required. Not nice !