Client-side scripting using JavaScript containers

Client-Side JavaScript is JavaScript code that runs directly in a user’s web browser rather than on a server. It’s what makes web pages interactive, dynamic, and responsive to user actions.^[1]

Script interface defines an HTML element for client-side scripting, usually JavaScript.

• ScriptsContainer class is a container for Script components
  • Script implementations → <script> tag:
  • ExternalScript object links to an external script file.
    • Best for: Large projects and shared logic.
    • Pros: Keeps HTML clean, allows the browser to cache the file for speed, and enables code reuse across multiple pages.
    • Cons: Requires an additional HTTP request to fetch the file.
  • InlineScript object contains inline scripting statements:
    • Best for: Small, page-specific snippets or quick fixes.
    • Pros: Loads instantly without an extra server request.
    • Cons: Hard to maintain and cannot be reused on other pages.
• The Console - provides access to the debugging console (e.g., the Web console in Firefox).^[2]
• Noscript - <noscript> defines a section of HTML to be inserted if a script type on the page is unsupported or if scripting is currently turned off in the browser.^[3]

NOTE!: The best practice of placing client side scripts is usually the end of the page, just inside the closing body tag. This guarantees that all of the DOM elements needed are already present on the page.^[4]