No, IIFE doesn’t execute the code in document ready. 1. Just in IIFE: (function($) { console.log(‘logs immediately’); })(jQuery); This code runs immediately logs “logs immediately” without document is ready. 2. Within ready: (function($) { $(document).ready(function(){ console.log(‘logs after ready’); }); })(jQuery); Runs the code immediately and waits for document ready and logs “logs after ready”. This … Read more
Yes, you can do that, it’s just a matter of scope. If you only need to access callMe() from within $(document).ready(function() { }), then it’s fine to put the function there, and offers some architecture benefits because you can’t access the function outside of that context. If you need to use the callMe() function outside … Read more
All three of the following syntaxes are equivalent: $(document).ready(handler) $().ready(handler) (this is not recommended) $(handler) Aliasing the jQuery Namespace When using another JavaScript library, we may wish to call $.noConflict() to avoid namespace difficulties. When this function is called, the $ shortcut is no longer available, forcing us to write jQuery each time we would … Read more
They are the same. Check out the jQuery .ready() docs. Here’s a quote from the docs: All three of the following syntaxes are equivalent: $(document).ready(handler) $().ready(handler) (this is not recommended) $(handler)
You will want to use the “ngAfterViewInit” lifecycle hook, through importing AfterViewInit (https://angular.io/docs/ts/latest/guide/lifecycle-hooks.html#!#afterview). You can use it as shown below: Installation: tsd install jquery –save or typings install dt~jquery –global –save Utilization: import { Component, AfterViewInit } from ‘@angular/core’; import * as $ from ‘jquery’; ngAfterViewInit() { this.doJqueryLoad(); this.doClassicLoad(); $(this.el.nativeElement) .chosen() .on(‘change’, (e, args) => … Read more
The ready event cannot fire twice. What is more than likely happening is you have code that is moving or manipulating the element that the code is contained within which causes the browser to re-execute the script block. This can be avoided by including script tags in the <head> or before the closing </body> tag … Read more
I spent some time on researching the same since JQM docs are not very detailed at this point. Solution below works fine for me: <script type=”text/javascript”> $(‘div:jqmData(role=”page”)’).live(‘pagebeforeshow’,function(){ // code to execute on each page change }); </script> You have to implement your own checking flow in order to prevent multiple initialization since the code above … Read more
To answer your question: No, document.ready will not fire again once a ajax request is completed. (The content in the ajax is loaded into your document, so there isn’t a second document for the ajax content). To solve your problem just add the event listener to the Element where you load the ajax content into … Read more
I got an official answer from one of the jQuery developers: $().ready(fn) only works because $() used to be a shortcut to $(document) (jQuery <1.4) So $().ready(fn) was a readable code. But people used to do things like $().mouseover() and all sorts of other madness. and people had to do $([]) to get an empty … Read more
It depends on how your $(‘site-header’) is constructed. You can try to use $timeout with 0 delay. Something like: return function(scope, element, attrs) { $timeout(function(){ $(‘.main’).height( $(‘.site-header’).height() – $(‘.site-footer’).height() ); }); } Explanations how it works: one, two. Don’t forget to inject $timeout in your directive: .directive(‘sticky’, function($timeout)