jQuery Forum

I did something similar once with ui-tabs and found that it doesn't port x-browsers:  Chrome would not touch the JS inside the innerHTML.  Honestly, I did not mind too much.  Working around this problem, I think I ended up with a much cleaner model.  I now load ALL the JS stuff in index.html.  All the late-loading JS stuff sits in functions which I only invoke upon Ajax.success (you need those closures anyway for namespace separation).  This worked very well with ui-tabs because it fires a "tabsload" event which I could bind all the late stuff to.  It did not work with ui-dialog but then, it doesn't support Ajax out of the box anyway.  Given that you are implementing the late-loading HTML part yourself, you might as well invoke your own isReady function upon .success.  In fact, I literally just completed something very similar:  I have icons firing ui-dialog which they populate with Ajax HTML that needs JS animation. 

When I tried some late-loading JS with ui-tabs, I found that Chrome would not run the code inside my <script> tag.  Opera, FF and IE were fine.  I did not test Safari but since it shares a lot of code with Chrome, it will probably fail too.  Perhaps some sort of security feature since it forces you to introduce all the "dangerous stuff" upfront.  As I said, I am not unhappy about this at all since it stopped me from going down a route that I hate: to get to where YOU want to be, you end up with HTML and JS code interspersed in one messy late-loading HTML file.  Instead, I do like so: