Hi Dharmendra,

Observed functionality is correct. Or better to say, that happens according to rules of browser related to object moved from one parent to another. The idea behind igDialog is to take content of target element, remove it from old parent and insert into dynamically created container of igDialog. If target element contains javascript statements, then after the move, a browser may decide to execute those statements.

When page is initially loaded, then browser loads content of body (including target-element designed for igDialog) and executes all possible javascripts: first alert appears.
After body was loaded, the ready-event of jquery is raised, igDialog is created and moves target element from old container to igDialog. That move triggers execute of javascripts located in target element and second alert appears.

All that is not related to visibility of igDialog, but only to change of target's parent. If parent would be moved twice (igDialog would be created/initialized twice), then alert would appear 3 times, etc.

If application needs only one alert, then it may add condition which validates layout of target-element: if target-element is inside igDialog or still outside. According to that condition alert can be displayed before move to igDialog or after: that may depend on logic/expectations of application.