I am using angular-animate.js in angularjs ui grid plugin. But in ie9 I am getting error "Function expected" in function fireDoneCallbackAsync(). Please see the attached screenshot. How can I handle this error and also I am not clear from which part of the code this error is being thrown.
Although most modern browsers have good support for CSS transitions and CSS animations, IE9 and earlier do not.
If you want animations that are backwards-compatible with older browsers, consider using JavaScript-based animations.
Described here in detail.
The problem was due to having different version of angular js and animate js. My animate js was 1.2.26, recently I update angular js to 1.3.15, that resulted this error. After updating animate js also to 1.3.15 has solved the problem.
Related
Angular Material fabSpeedDial is not working in Andriod Mobile.
(Important Note:ISSUE OCCURS IN ANDRIOD MOBILE ONLY WHEN I USE, jquery-2.2.3.min.js)
I have a demo code taken from the following codepen link
Angular Material fabSpeedDial
If i remove that jquery-2.2.3.min.js, then the functionality works fine both in mobile and desktop.
But iam in a situation where i cannot remove this jquery-2.2.3.min.js. I also tried having lower version of jquery like 2.2.2 , 2.2.1 etc, but same results.
Please help me in finding a solution for this problem.
This issue is fixed after updating angular-material.js to v0.11.2
I just updated the version of Angular Material I am using to 1.0.6
Now when I use md-select + md-option, although all the correct options and corresponding md-option DOM elements display in the inspector, the drop down list does not display upon click, and instead the page (Chrome browser) freezes completely. No console error is thrown.
Here is my code:
md-select(
aria-label='select number of seats'
ng-show="bookable.seatsperbooking>1"
ng-model="appt.seats")
md-option(
ng-repeat='num in getnumber(seatsallowed) track by $index'
value='{{num}}') {{ num }}
and here is a screenshot of the inspector, which shows the correct number of option DOM elements:
screenshot of options
This was happening because the Angular + Angular Material versions I was using were incompatible. Angular Material 1.0.7 seems to require at least Angular 1.4 (Angular Material 1.0.7 was not working with Angular 1.3.20)
Having same problem.
After updating AngularJS to newer version 1.5.5 (w/ Angular Material 1.0.7) solved the problem.
Same issue here. I have Angular Material 1.1.0.
Updated Angular from 1.3.15 to 1.5.8. Fixed.
Just started a demo Angular2 project (no previous experience with Angular1/AngularJS. Have followed and extended from the online quickstart and tutorials, and all was fine. However I'm at the point where I would like to use some components from a library which is designed for AngularJS, and having no end of problems!
Most of the information available about AngularJS/Angular2 compatibility assumes that you have an AngularJS project that you're adding Angular2 components to - not the other way around - so what I'm hoping to do may not even be possible. What I've tried so far involves a simple stripped-back project based on the Angular2 quickstart, with a single Angular2 component that loads into the index.html. I'd then like to integrate components from the existing library (AngularJS-based) into this.
I've tried using UpgradeAdapter.upgradeNg1Component to create components from the library and add them directly into my Angular2 component
I've tried installing angularjs through npm, importing it in a script tag into my index.html and then using a combination of UpgradeAdapter.downgradeNg2Component and UpgradeAdapter.bootstrap to load my Angular2 as a downgraded module
Neither of these seem to work - the component fails to show, and the browser console tells me I've got an Uncaught SyntaxError: Unexpected token <
Evaluating http://localhost:3000/angular2/upgrade
Error loading http://localhost:3000/app/main.js
My best guess at the moment is that this is actually an unsupported scenario, and I need to have a 'proper' AngularJS app in order to use the UpgradeAdapter functionality from Angular2. Can anyone confirm this? Or is there something stupid I'm missing here?
Here is a working plunkr describing how to mix Angular1 and Angular2 elements:
http://plnkr.co/edit/yMjghOFhFWuY8G1fVIEg?p=preview
An important point is to bootstrap your main component on the UpgradeAdapter. This way all elements are available in providers (services / factories) and in directives (components / directives):
upgrade.bootstrap(document.body, ['heroApp']);
These two answers could help you:
angular 1.x and angular2 together
How to inject upgraded Angular 1 service/factory to Angular 2 component in ES5?
So the major problem in this case turned out to be the fact that it appears that the upgrade components aren't included as part of the basic angular 2 bundle. After adding:
<script src="node_modules/angular2/bundles/upgrade.min.js"></script>
to my index.html file the error I was seeing disappeared.
Thanks to the answer here for pointing me in the right direction!
I recently had to upgrade my Ionic app's version [as I migrated to a different machine], everything worked well and as expected in the app with the exception of animations. All the angular (angular animate) based animations I had no longer work! They were basically CSS transitions applied to the .ng-enter and .ng-leave classes.
I was wondering if this problem has something to do with Ionic now using angular v1.4.3? I read here and here that it's a bug associated with the 1.4.x versions of angular?
Has this issue been reported before? if so... is there a workaround?
Thanks in advance!
Has anyone gotten the Angular JS ui-router quick-start to run in IE8? The quick start's here:
ui-router quick-start
It's working in chrome but not in IE8.
Thanks!
[Edit]
I have read the ie documentation under angular js but the fix provided doesn't seem to fix the issue (missing forEach method). The fix only addresses issues with angular js and not angular-ui-router.
The only thing that works is from an answer here: AngularJS - IE8 html template. The basically provides an implementation for forEach which is not supported in IE.
Can you try building off of master? There was a pull request merged just after the last release (https://github.com/angular-ui/ui-router/pull/392) that resolved some IE8 issues. Everything else should work fine AFAIK.