Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
AngularJs site doesn't seem to work in FireFox
Message
De
05/11/2014 12:24:00
 
 
Information générale
Forum:
Javascript
Catégorie:
Compatibilité Cross-browser
Divers
Thread ID:
01610488
Message ID:
01610545
Vues:
38
This message has been marked as a message which has helped to the initial question of the thread.
>>>Hi everybody,
>>>
>>>I've been testing our site in Google Chrome and IE and it seems to be working Ok in these 2 browsers. I didn't touch the code for a few days, got the very latest code (from other developers) and got some strange appearance (looks like changes in css to me).
>>>
>>>Anyway, my colleague told me he can not open a particular form in FireFox. I installed latest FireFox and tried opening the site and that particular form and I could not open it either. I am also getting other errors in other areas.
>>>
>>>Say, these are 2 errors which I see when I try any form:
>>>
>>>Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead jquery.js:1
>>>Use of getPreventDefault() is deprecated. Use defaultPrevented instead.
>>>
>>>Do you know what am I supposed to do with these 2? They seem to point to jquery files.
>>>
>>>I am also getting another error (this time preventing a form from opening):
>>>
>>>"Error: $scope.metaData is undefined
>>>loadTemplate/<@http://localhost:5525/Areas/Items/Scripts/Controllers/TemplateController.js:470:21
>>>qFactory/defer/deferred.promise.then/wrappedCallback@http://localhost:5525/Scripts/angular.js:10924:31
>>>qFactory/ref/<.then/<@http://localhost:5525/Scripts/angular.js:11010:26
>>>$RootScopeProvider/this.$get</Scope.prototype.$eval@http://localhost:5525/Scripts/angular.js:11930:16
>>>$RootScopeProvider/this.$get</Scope.prototype.$digest@http://localhost:5525/Scripts/angular.js:11756:15
>>>$RootScopeProvider/this.$get</Scope.prototype.$apply@http://localhost:5525/Scripts/angular.js:12036:13
>>>done@http://localhost:5525/Scripts/angular.js:7827:34
>>>completeRequest@http://localhost:5525/Scripts/angular.js:8009:7
>>>createHttpBackend/</xhr.onreadystatechange@http://localhost:5525/Scripts/angular.js:7965:1
>>>"
>>>--------------------------------
>>>I know that this same form works in Google Chrome and IE.
>>>
>>>FireFox seems to be more strict than other 2 browsers. Do you know what should I do with these errors? I am also going to ask my colleagues to test in FireFox and share their findings.
>>
>>The first two are warnings not errors and wouldn't affect execution. The solution to the last error is what we've been telling you all along - DEBUG
>
>I know that the first 2 are warnings but I'd rather not have them anyway. Do you know where this originates from and is it possible to fix? Are you getting them as well?

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.....
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform