dhtml

In a webpage I am calling a WebService that gives me an integer value. I need to display this value in a block of text. I am currently using an HTML <span> . So far, I've found two methods of putting my value in a span. innerText() is an IE proprietary way of doing it and innerHTML() is a non-standards compliant way, although widely supported. What is the correct standards compliant way of setting the text between <span> and </span> from Javascript? This is standards compliant and cross-browser safe. Example: http://jsfiddle.net/kv9pw/ var span = document.getElementById('someID'); while( span

I'm trying to figure out the most performant way of deep-cloning a DOM tree within the browser. If I start out with var div = document.getElementById("source"); var markup = div.innerHTML; What will be faster, var target = div.cloneNode(true); or var target = document.cloneNode(false); target.innerHTML = markup; I understand the browser platform may make a big difference here, so any information about how these compare in the real world would be appreciated. Let's test! I added the following code to a copy of StackOverflow's Questions page (removing existing scripts first, and running from

There are some attributes in HTML which are "boolean" - browsers treat them as "true" if they are present, regardless of the value. An example of such an attribute is selected on the <option> tag. Another is checked on <input type="checkbox"> . If you have a call to setAttribute() for such an attribute, there seems to be no value you can set to have the browsers consistently behave as though the attribute is missing. For example option.setAttribute("selected", false) will still mark the option selected. null , empty string or undefined don't work either. If anyone knows of a value I can set to

In answering another question I became aware that my Javascript/DOM knowledge had become a bit out of date in that I am still using escape / unescape to encode the contents of URL components whereas it appears I should now be using encodeURIComponent / decodeURIComponent instead. What I want to know is what is wrong with escape / unescape ? There are some vague suggestions that there is some sort of problem around Unicode characters, but I can't find any definite explanation. My web experience is fairly biased, almost all of it has been writing big Intranet apps tied to Internet Explorer. That

I am creating a photo gallery, and would like to be able to change the query string and title when the photos are browsed. The behavior I am looking for is often seen with some implementations of continuous/infinite page, where while you scroll down the query string keeps incrementing the page number ( http://x.com?page=4 ) etc.. This should be simple in theory, but I would like something that is safe across major browsers. I found this great post , and was trying to follow the example with window.history.pushstate , but that doesn't seem to be working for me. And I'm not sure if it is ideal