Skip to main content

Difference between document.ready and window.onload/load event

$(document).ready():-
Jquery $(document).ready()  function called once the DOM (Document object model) is loaded on your page. DOM means the entire html tags/script (i.e. div, table, paragraph etc.). If your web page has large images, it will not wait for loading of images completely. This method is used when we want to initialize our jQuery codes after the DOM is ready.

$(document).ready(function(){
 // method called as soon as DOM is ready
});

window.onload()/load() method:-
The load event fires when all the content on your page loaded including the DOM (document object model) and images. This method gets called when images and all associated resources including the DOM (document object model) of the page have been fully loaded. Suppose your web page has large size images then until all the images are not fully loaded on the page, this method will not called.

$(window).load(function () {
    //this method called after images are loaded 
});

This method is called each and every partial postback of update panel but $(document).ready() is not called each and every partial postback of update panel. $(document).ready() is called only one time (during first time of page loading). Hence code written in $(document).ready() method will not be initialized each and every partial postback.

So let’s see what the differences between these two methods are:

$(document).ready()
window.load()
$(document).ready() is best for one time initialization.
This method is not best for onetime initialization if used with UpdatePanel.
We can have multiple document.ready() methods on a web page that will be called in coming sequence.
We can have only one onLoad() method on a web page.
This method is called as soon as DOM is ready.
This method is called once entire DOM resources are loaded including images
This method is called slightly before than onLoad().
This method is called slighty after the $(document).ready().
It supports cross browser compatibility.
Not Cross browser compatible.
Unable to re-attach the functionality to elements/controls of the page affected by partial postbacks.
Best to re-attach the functionality to elements/controls of the page affected by partial postbacks with UpdatePanel.
Labels:

Comments

  1. AnonymousMay 21, 2014 at 10:15 AM

    best and simple for learning and great work

    ReplyDelete

Post a Comment

Popular posts from this blog

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...
Post a Comment
Read more

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J
4 comments
Read more

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...
Post a Comment
Read more