Skip to content Skip to sidebar Skip to footer

Why Would I Put An ID On A Script Tag?

I've noticed that some web developers put IDs on scripts tags. For example: I know that accor

Solution 1:

The one use I've seen of this is if you want to provide widget for customers and you instruct them to place the <script> tag wherever they want the widget to show up. If you give the <script> element an ID then you can reference that inside of it to place the code in the right place. That's not to say that it is the only way of achieving that, of course, but I've seen it done and suggested it in the past.


Solution 2:

I've seen it used for Microtemplating, where you can put a template in a script tag and then reference it through the ID.

Here's great post with javascript microtemplating by John Resig - note that this is not the ONLY way of achieving this, only Johns version of it.


Solution 3:

The benefit is that you can refer to the element with an id="foo" using the global variable window.foo or just foo:

id as a global variable


Solution 4:

By using an ID, you can wait on the specific JS file to finish loading. FB does this

(function(d, s, id){
    var js, fjs = d.getElementsByTagName(s)[0];
    if (d.getElementById(id)){ return; }
    js = d.createElement(s); js.id = id;
    js.onload = function(){
        // remote script has loaded
    };
    js.src = "//connect.facebook.net/en_US/sdk.js";
    fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));

facebook-jssdk being their unique identifier.

[https://stackoverflow.com/a/8578840][1]


Post a Comment for "Why Would I Put An ID On A Script Tag?"