Talk:Web Science/Part1: Foundations of the web/Dynamic Web Content/Client side JavaScript

Join the discussion: Ask and questions and provide answers edit

  • If you click the ask a question button you're question will appear at the bottom of this list.
  • If you click the give an answer you will be able to provide an answer to the questions that have been asked so far.


Different JS-implementations are a problem edit

"Most browsers have different implementations since JavaScript has never been standardized" - this may be true but where do problems arise from this? I know from browsers handling markup and stylesheets extremely different (I'm looking at you, Internet Explorer) but I have not yet experienced different JS-behaviour. The only real differences I have noticed were in terms of speed. --Onse (discusscontribs) 23:05, 24 November 2013 (UTC)Reply

Some browsers really have different implementations of JavaScript (example below). What I do not like in this question is: since JavaScript has never been standardized. JavaScript is standardized. --oleamm (discusscontribs) 01:23, 16 February 2014 (UTC)Reply
var xmlhttp;
if (window.XMLHttpRequest)
  {// code for IE7+, Firefox, Chrome, Opera, Safari
  xmlhttp=new XMLHttpRequest();
  } else
  {// code for IE6, IE5
  xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
  }
Return to "Web Science/Part1: Foundations of the web/Dynamic Web Content/Client side JavaScript" page.