Optimize plugin wrapper

[fkloft]

Is there a specific reason to append

var script = document.createElement('script');
script.appendChild(document.createTextNode('('+ wrapper +')();'));
(document.body || document.head || document.documentElement).appendChild(script);

after each plugin instead of calling wrapper() directly?

The current implementation has some major drawbacks. The code is first parsed, then wrapper.toString() is implicitly called to add the source into the <script> element, which is then parsed again. This is

• slower than calling wrapper() directly (no re-parsing)
• makes it impossible to debug the code. The JS parser cannot know which file a specific line of code is from and most debuggers cannot step into dynamically inserted scripts.

[jonatkins]

The same applies to the main IITC script too (end of main.js)

I believe it's done like this so all the code runs within the context of the page itself, rather than any separate context used by Greasemonkey/Tampermonkey