{"id":58,"date":"2006-02-06T00:32:24","date_gmt":"2006-02-06T05:32:24","guid":{"rendered":"http:\/\/www.killersites.com\/blog\/?p=58"},"modified":"2017-02-23T10:10:57","modified_gmt":"2017-02-23T15:10:57","slug":"going-beyond-web-standards","status":"publish","type":"post","link":"https:\/\/www.killersites.com\/blog\/2006\/going-beyond-web-standards\/","title":{"rendered":"When breaking from the Web standards makes sense."},"content":{"rendered":"

\"\"<\/strong><\/p>\n

INTRODUCTION<\/strong><\/p>\n

Following the Web Standards makes perfect sense when it allows you to build easy to mantain websites that work with the major browsers. It doesn’t make sense when using Web Standards forces you to use hacks, prevents you from taking advantage of a great technology\/feature or makes your job as a web designer or developer more difficult.<\/p>\n

Let’s take a look at 3 very useful technologies that are not in the Web Standards, but do not have any of the negative consequences associated with browser specific code:<\/p>\n

    \n
  1. IE conditional comments:<\/strong> for cross-browser CSS layouts. <\/li>\n
  2. AJAX – using the XMLHTTPobject:<\/strong> for behind the scenes browser to server communication. <\/li>\n
  3. The innerHTML property:<\/strong>  for quick and easy DOM manipulation. <\/li>\n<\/ol>\n

    Though each of the above are not part of the Web Standards, they provide terrifically useful functionality without any hangups.<\/p>\n

    IE CONDITIONAL COMMENTS<\/strong><\/p>\n

    Though IE conditional comments only work in IE, it makes great sense to use them when you want to isolate code. Since all other browsers will see IE conditional comments as being only HTML comments, there can never be a down side to IE conditional comments. It is the proper way of dealing with IE 6’s problems with CSS code.<\/p>\n

    Example:<\/strong><\/p>\n

    <head><\/p>\n

    <link href="standardStyle.css" rel="stylesheet" type="text\/css" media=screen><\/p>\n

    <!–[if IE 6]>
    <link href="ie_style.css" rel="stylesheet" type="text\/css" media=screen>
    <![endif]–><\/p>\n

    <\/head><\/p>\n

    In the above example, we use IE conditional comments to hide IE specific CSS from all other browsers. Spefically, the IE conditional comments:<\/p>\n

     (<!–[if IE 6]> and <![endif]–>) <\/p>\n

    is loading the ‘ie_style.css’ style sheet only if the browser reading the page is IE6. <\/p>\n

    IE conditional comments are a replacement for dangerous CSS hacks that are commonly used to deal with IE’s occasional problems with standard CSS.<\/p>\n

    AJAX<\/strong><\/p>\n

    The heart of AJAX is in the XMLHTTPObject – a JavaScript function built into every major browser but is NOT part of the Web Standards. Given how powerful AJAX is, and given how popular it has become, you can be sure that every major browser will continue to support it. <\/p>\n

    So as a Web Standards zealot, you have to ask yourself whether blind adhereance to the Web standards is worth missing out on this important tool? That is to say, if you’re a web standards zealot, you couldn’t\/shouldn’t use AJAX since it is not part of the official Web standards … it’s your choice. <\/p>\n

     INNER HTML PROPERTY<\/strong><\/p>\n

    InnerHTML is an easy to use property supported by all the major browsers that allows you to dynamically update\/change web pages without having to do a page refresh. <\/p>\n

    Example using innerHTML:<\/strong><\/p>\n

    var targetDiv = document.getElementById("targetDiv");
    targetDiv.innerHTML = "<p>innerHTML is fast and easy!<\/p>"<\/p>\n

    Example using DOM methods:<\/strong><\/p>\n

    var para = document.createElement("p");
    var targetDiv = document.getElementById("targetDiv");
    targetDiv.appendChild(para);
    var txt = document.createTextNode("Dom methods are much longer than innerHTML");
    para.appendChild(txt);<\/p>\n

    As you can see with the above examples, to insert text with DOM methods takes a lot more code than innerHTML. So, should you use innerHTML?<\/p>\n

    The answer:<\/strong> Browser makers typically don’t remove functionality, and given that innerHTML is supported by all the browsers and is easy to use, this is yet another example where I will break from the standards and feel comfortable about it.<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    3 examples of when going beyond the Web Standards makes sense.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/posts\/58"}],"collection":[{"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":2,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"predecessor-version":[{"id":4820,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/posts\/58\/revisions\/4820"}],"wp:attachment":[{"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.killersites.com\/blog\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}