3
Deprecated Angular Calls in SmarterMail 16
Problem reported by John Marx - 7/20/2017 at 10:09 AM
Submitted
The more I use the web interface to combat end user complaints as I am trying to help. The very first item in Google developer tools states that the angular calls being used are deprecated due to poor end user experience. Not saying that this is solely the culprit but I know when I am developing anything deprecated I work on removing.
 
angular-v-16.0.6397.16007.8d4c515eef37400.js:4 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
 
Signalr onDisconnect Called
site-v-16.0.6397.16007.8d4c515eef37400.js:93 Signalr Disconnected
site-v-16.0.6397.16007.8d4c515eef37400.js:93 SignalR Init2, Connected: undefined
site-v-16.0.6397.16007.8d4c515eef37400.js:93 SignalR Start2
site-v-16.0.6397.16007.8d4c515eef37400.js:93 SignalR Started2
site-v-16.0.6397.16007.8d4c515eef37400.js:93 SignalR connection type: webSockets
site-v-16.0.6397.16007.8d4c515eef37400.js:5 SignalR Initted, Sending connect with auth details.
site-v-16.0.6397.16007.8d4c515eef37400.js:5 SignalR Connect success.
DevTools failed to parse SourceMap: http://mail.jm2marketing.com/interface/output/angular.js.map
DevTools failed to parse SourceMap: http://mail.jm2marketing.com/interface/output/vendor.js.map
DevTools failed to parse SourceMap: http://mail.jm2marketing.com/interface/output/site.js.map
vendor-v-16.0.6397.16007.8d4c515eef37400.js:458 [Deprecation] Using the Notification API on insecure origins is deprecated and will be removed in M61, around September 2017. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
o.show @ vendor-v-16.0.6397.16007.8d4c515eef37400.js:458
e @ site-v-16.0.6397.16007.8d4c515eef37400.js:73
(anonymous) @ angular-v-16.0.6397.16007.8d4c515eef37400.js:139
$eval @ angular-v-16.0.6397.16007.8d4c515eef37400.js:153
$digest @ angular-v-16.0.6397.16007.8d4c515eef37400.js:150
$apply @ angular-v-16.0.6397.16007.8d4c515eef37400.js:153
(anonymous) @ angular-v-16.0.6397.16007.8d4c515eef37400.js:166
f @ angular-v-16.0.6397.16007.8d4c515eef37400.js:52
(anonymous) @ angular-v-16.0.6397.16007.8d4c515eef37400.js:55
angular-v-16.0.6397.16007.8d4c515eef37400.js:127 $mdDialog: using `<md-dialog ng-cloak>` will affect the dialog opening animations. <div class=​"md-dialog-container" tabindex=​"-1" md-theme style=​"top:​ 0px;​ height:​ 1014px;​">​…​</div>​
(anonymous) @ angular-v-16.0.6397.16007.8d4c515eef37400.js:127
E @ vendor-v-16.0.6397.16007.8d4c515eef37400.js:26
(anonymous) @ vendor-v-16.0.6397.16007.8d4c515eef37400.js:25
u @ angular-v-16.0.6397.16007.8d4c515eef37400.js:141
$ @ vendor-v-16.0.6397.16007.8d4c515eef37400.js:25
(anonymous) @ vendor-v-16.0.6397.16007.8d4c515eef37400.js:25
(anonymous) @ angular-v-16.0.6397.16007.8d4c515eef37400.js:139
$eval @ angular-v-16.0.6397.16007.8d4c515eef37400.js:153
$digest @ angular-v-16.0.6397.16007.8d4c515eef37400.js:150
$apply @ angular-v-16.0.6397.16007.8d4c515eef37400.js:153
l @ angular-v-16.0.6397.16007.8d4c515eef37400.js:106
t.onload @ angular-v-16.0.6397.16007.8d4c515eef37400.js:111
 
 
 

Reply to Thread