I agree the user should decide to run the code or not, as well as for the user to replace the code with their own if they want to modify it.
Sometimes scripts can be used to implement something, but just to display text and so on, should not need a script; it should just have the text. (Often they like to put in so many pictures, styles, scripts, etc, that you do not need. Just put the text!)
(Some things might be other protocol and try to make a HTML interface to it, but even then the protocol should be documented without requiring such scripts to read it and you can access it directly and don't have to use their implementation. For example if they use gopher or NNTP or telnet then you can just use those directly and the URL should link to them directly rather than requiring the HTML.)
One thing to do for web pages that use specific scripts is to define a new attribute to specify the unversal ID of a widget or program so that you can more easily substitute your own implementation or use it in web browsers that do not implement JavaScript.
Sometimes scripts can be used to implement something, but just to display text and so on, should not need a script; it should just have the text. (Often they like to put in so many pictures, styles, scripts, etc, that you do not need. Just put the text!)
(Some things might be other protocol and try to make a HTML interface to it, but even then the protocol should be documented without requiring such scripts to read it and you can access it directly and don't have to use their implementation. For example if they use gopher or NNTP or telnet then you can just use those directly and the URL should link to them directly rather than requiring the HTML.)
One thing to do for web pages that use specific scripts is to define a new attribute to specify the unversal ID of a widget or program so that you can more easily substitute your own implementation or use it in web browsers that do not implement JavaScript.