Unobtrusive JavaScript

Unobtrusive JavaScript is a general approach to the use of JavaScript in web pages. Though the term is not formally defined, its basic principles are generally understood to include separation of functionality (the "behavior layer") from a Web page's structure/content and presentation,[1] and progressive enhancement to support user agents that may not support certain JavaScript functionality and users that have disabled JavaScript.[2]

Part of a series on
JavaScript
Language
Libraries
Implementations
See also

Overview

The emergence of standards-compliant browsers, JavaScript frameworks, and high-quality debugging tools have made organized, scalable JavaScript code possible, and the emergence of Ajax interfaces has made it desirable. Whereas JavaScript was once reserved for relatively simple and non-critical tasks such as form validation and decorative novelties, it is now used to write large, complex codebases that are often part of a site's core functionality.

The concept of "unobtrusiveness" in relation to JavaScript programming was coined in 2002 by Stuart Langridge[3] in the article "Unobtrusive DHTML, and the power of unordered lists".[4] In the article Langridge argued for a way to keep all JavaScript code, including event handlers, outside of the HTML. Stuart Langridge has since expanded upon this thought in book[5] and article format.[6]

Other authors have tried to refine and define the essential elements of unobtrusiveness. David Flanagan's book JavaScript: The Definitive Guide said that while there is no specific formula, there are three main goals:

  • To separate JavaScript from HTML markup, as well as keeping modules of JavaScript independent of other modules.
  • Unobtrusive JavaScript should degrade gracefully—all content should be available without all or any of the JavaScript running successfully.
  • Unobtrusive JavaScript should not degrade the accessibility of the HTML, and ideally should improve it, whether the user has personal disabilities or are using an unusual, or unusually configured, browser.[7]

The Web Standards Project described four benefits of unobtrusive DOM scripting in their JavaScript Manifesto.

  1. Usability: An unobtrusive DOM script does not draw the attention of the user—visitors use it without thinking about it.
  2. Graceful degradation: Unobtrusive DOM scripts never generate error messages, in any browser, even when they fail. If features cannot be presented properly, they silently disappear.
  3. Accessibility: If any script fails, the page still delivers its core functions and information via the markup, stylesheets and/or server-side scripting.
  4. Separation: For the benefit of other and future web developers, all JavaScript code is maintained separately, without impacting other files of script, markup or code.[8]

For the Paris Web Conference in 2007, Christian Heilmann identified seven rules of Unobtrusive JavaScript.[9]

  1. Do not make any assumptions: Defensive programming techniques should allow for the possibilities that JavaScript may not run, the browser may not support expected methods, the HTML may have changed, unexpected input devices may be in use and other scripts may either not be present or may be encroaching on the global namespace.
  2. Find your hooks and relationships, such as IDs and other aspects of the expected HTML.
  3. Leave traversing individual DOM objects to the experts, such as to the CSS handler built into the browser where possible.
  4. Understand browsers and users, particularly how they fail, what assumptions they make, and unusual configurations or usages.
  5. Understand events, including how they 'bubble' and the features of the Event object that is passed to most event handlers.
  6. Play well with other scripts by avoiding global function and variable names.
  7. Work for the next developer by using self-explanatory variable and function names, creating logical and readable code, making dependencies obvious, and commenting any code that still might confuse.

Separation of behavior from markup

Traditionally, JavaScript was often placed inline together with an HTML document's markup. For example, the following is a typical way to register a JavaScript event handler in HTML:

<input type="text" name="date" onchange="validateDate()" />

The purpose of HTML markup is to describe a document's structure, not its programmatic behavior. Combining the two can negatively impact a site's maintainability, like combining content and presentation.[10] JavaScript behavior created and referenced in the HTML can be harder to use and maintain, for example when setting handlers for several events on a single element, when setting the same event handler on several elements, or when using event delegation.

The unobtrusive solution is to register the necessary event handlers programmatically, rather than inline. Rather than adding an onchange attribute explicitly as above, the relevant element(s) are simply identified, for example by class, id or some other means in the markup:

<input type="text" name="date" id="date" />

A script that runs when the page is first loaded into the browser can then look for each relevant element and set it up accordingly:

window.addEventListener("DOMContentLoaded", function(event) {
    document.getElementById('date').addEventListener("change", validateDate);
});

Namespaces

Unobtrusive JavaScript should add as little as possible to the global object or global namespace of the environment in which it runs. Other scripts may override any variable or function that is created in the global namespace, and this can lead to unexpected failures that are difficult to debug. JavaScript does not have a built-in explicit namespace mechanism, but the desired effects are easy to produce using the language's facilities. Flanagan suggests the use of the developer's own domain name, dotted segments reversed, as a single global name to publish that is very likely to be unique, in the style developed in the Java language.[11]

var org = org || {};
if (typeof org !== 'object') {
    throw new Error("org already defined as non-object");
}

org.example = org.example || {};
if (typeof org.example !== 'object') {
    throw new Error("org.example already defined as non-object");
}

While variables, functions and objects of all kinds can be further defined within such namespace objects, it is usually recommended to use closures within the namespace to further isolate what will become private variables and functions, as well as to export what will be the public interface of each module of functionality. The code above could be followed directly by the following, which uses an IIFE to establish its closure:[9]

org.example.Highlight = (function() {
    // Define private data and functions
    var highlightId = 'x';
    function setHighlight(color) { 
        document.getElementById(highlightId).style.color = color;
    }
    
    // Return public pointers to functions or properties
    // that are to be public.
    return {
        goGreen: function() { setHighlight('green'); },
        goBlue:  function() { setHighlight('blue'); }
    }
}()); // End of closure

From any other module, these public methods could be invoked in either way as follows

org.example.Highlight.goBlue();

var h = org.example.Highlight;
h.goGreen();

In this way, each module-writer's code is contained in private or in a unique namespace and cannot interfere with or intrude upon any other code at any time.

Degrading gracefully
Main article: Graceful degradation

Writing an event listener that detects the loading of the HTML page and then adds relevant listeners to other events on the page, as well as other behaviors as required, can solve the problem of separating JavaScript functionality from HTML markup. The use of client-side JavaScript libraries such as jQuery, MooTools or Prototype can simplify this process and help ensure that individual browser and browser version implementation details are hidden and catered for. Keeping most of the JavaScript out of the default namespace helps ensure that it is as unobtrusive as possible in that sense. A further criterion of unobtrusive JavaScript that is often cited is to ensure that added behavior degrades gracefully on those browsers with unexpected configurations, and those on which the user may have disabled JavaScript altogether.[7]

This requirement is a basic tenet of web accessibility, to ensure that JavaScript-enhanced websites are not only usable by people of all abilities and disabilities but that all users—whatever their computing platform—get equal access to all the site's information and functionality. Sometimes there is extra work involved in achieving this, but web accessibility is not an optional extra in many countries. For example, in the UK, the Equality Act 2010, while it does not refer explicitly to website accessibility, makes it illegal to discriminate against people with disabilities and applies to anyone providing any service in the public, private and voluntary sectors.[12] While a lot of effort may be put into designing and implementing a slick client-side user interface in unobtrusive JavaScript, it will not remain unobtrusive to a user without client-side scripting if they find that they cannot access published information. To meet this goal, it is often necessary to implement equivalent, albeit clunkier, server-side functionality that will be available without the use of JavaScript at all.

Take, for example, a webpage where thumbnail images need JavaScript behaviours so that full-size images will appear in front of the page when the mouse is rolled over them or they are clicked. First, server-side markup should ensure that the relevant full-size image is served to users without JavaScript who click on a thumbnail. In this case the basic HTML markup may look like the following, for each thumbnail:

<a href="fullsize-image-001.png" class="manual-link" title="Click for full-size image">
  <img src="image-001-thumb.png" class="thumb" width="50" height="50" alt="Image 1 shows... etc">
</a>

This will work as it is without JavaScript. Unobtrusive JavaScript, in this case, during page-load, could find all the a elements that have a class of manual-link and remove them from the page DOM. It could then find all the images of class thumb and attach an onmouseover or an onclick event handler that is specified in-line to provide the slick behaviour. For example, when invoked the event handler may send an Ajax request to the server for the full-size image, then add a div to the page DOM invoking existing CSS so it appears in front of existing content, which itself may become partially greyed out. The div will need a close button, perhaps a visual 'spinner' to show that data is loading, etc. Finally, when the Ajax data arrives, the handler hides the spinner and inserts the full-size image into the new div for display.

This way, all the client-side functionality depends on the same JavaScript function. If that function succeeds, it begins by removing the basic, manual behavior, and goes on to add the client-side scripted behavior. If the script fails for whatever reason, the manual behavior remains in place and remains functional.

Best practices

Though the essence of unobtrusive JavaScript is the concept of an added separate behavior layer, its advocates generally have subscribed to a number of related principles, such as:

See also

References
  1. Keith, Jeremy (2006-06-20). "Behavioral Separation".
  2. Olsson, Tommy (2007-02-06). "Graceful Degradation & Progressive Enhancement".
  3. "Building dynamic websites". 2006-08-09. Retrieved 2010-05-18.
  4. Langridge, Stuart (November 2002). "Unobtrusive DHTML, and the power of unordered lists". Retrieved 2008-08-07.
  5. Langridge, Stuart (2005). DHTML Utopia:Modern Web Design Using JavaScript & DOM. SitePoint. ISBN 0-9579218-9-6. (Reference to the first edition, since it shows how the author pioneered the concept.)
  6. E.g.: Langridge, Stuart (2005-06-01). "DHTML Utopia: Modern Web Design Using JavaScript & DOM". Retrieved 2016-10-18.
  7. Flanagan, David (2006). JavaScript: The Definitive Guide (5th ed.). O'Reilly & Associates. p. 241. ISBN 0-596-10199-6.
  8. "The JavaScript Manifesto". The Web Standards Project. Retrieved 8 Feb 2011.
  9. Heilmann, Christian (2007). "The seven rules of Unobtrusive JavaScript". Archived from the original on 2 May 2011. Retrieved 8 February 2011.
  10. "The web standards model – HTML CSS and JavaScript". W3C Web Standards Curriculum. W3C. 2014. Retrieved 16 May 2016.
  11. Flanagan, David (2006). "10". JavaScript: The Definitive Guide (5th ed.). O'Reilly & Associates. ISBN 0-596-10199-6.
  12. "Equality Act 2010". Her Majesty’s Stationery Office. Retrieved 7 September 2011.
  13. "Dev.Opera — Using Capability Detection". Retrieved 19 October 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.