cursor at the end of textbox problem in IE8

Sometimes it is nice to be able to insert the cursor at a specific location within a textbox. The most common purpose for this, in my opinion, is with textareas. For a theoretical example, I will explain a scenario I have run into a few times. I have already typed a paragraph into a textarea for comments, a message, whatever. For whatever reason, I go back up on the form and change a different field, and then tab back down to the text area. By default, it highlights the whole body of text within the textarea. But, I wanted to append some text what was there! Now I either have to grab my mouse and click at the end of the box or use a series of keystrokes to get the caret back to where I need it.
 
Ok fine, so maybe I am getting way too particular here.  But it really is a minor annoyance to me.  Granted, I could easily live with it, but I have come up with a solution instead. It would be best (again, this is my opinion) to programmatically force the cursor to jump to the end of the text area when it receives focus. I would not disagree that in some cases it can be rather convienent to have it it highlight the value on focus. But, for textareas, I just can not agree with it.
 
Anyways, that is how I got around to creating this generic function that will allow you to insert the caret at any position of a textbox or textarea that you wish... 
 
function setCaretPosition(elemId, caretPos) {
    var elem = document.getElementById(elemId);
 
    if(elem != null) {
        if(elem.createTextRange) {
            var range = elem.createTextRange();
            range.move('character', caretPos);
            range.select();
        }
        else {
            if(elem.selectionStart) {
                elem.focus();
                elem.setSelectionRange(caretPos, caretPos);
            }
            else
                elem.focus();
        }
    }
}
 
 
The first expected parameter is the ID of the element you wish to insert the cursor on. If the element is unable to be found, nothing will happen (obviously). The second parameter is the caret positon index. Zero will put the cursor at the beginning. If you pass a number larger than the number of characters in the elements value, it will put the cursor at the end.
 
I have tested it on several browsers; it works beautifully on IE6 and up, Firefox 2, Opera 8, Netscape 9, SeaMonkey, and Safari. Unfortunately on Safari it does not work in combination with the onfocus event (sigh).  If anybody out there has quick access to some older browsers (or any browser not mentioned above) and a few moments to test it, I'd really appreciate it if you let me know if it works or not.
 
Keep in mind that the above function could potentially be used for several different purposes. Even though my original purpose was somewhat impractical, there is definite potential for this function! Here is the unobtrusive example of using it to apply my original purpose: force the cursor to jump to the end of all textareas on the page when they receive focus...
 
function addLoadEvent(func) {
    if(typeof window.onload != 'function') {
        window.onload = func;
    }
    else {
        if(func) {
            var oldLoad = window.onload;
 
            window.onload = function() {
                if(oldLoad)
                        oldLoad();
 
                func();
            }
        }
    }
}
 
// The setCaretPosition function belongs right here!
 
function setTextAreasOnFocus() {
/***
 * This function will force the cursor to be positioned
 * at the end of all textareas when they receive focus.
 */
    var textAreas = document.getElementsByTagName('textarea');
 
    for(var i = 0; i < textAreas.length; i++) {
        textAreas[i].onfocus = function() {
            setCaretPosition(this.id, this.value.length);
        }
    }
 
    textAreas = null;
}
 
addLoadEvent(setTextAreasOnFocus);
 
I am going to make an effort to include an unobtrusive example with all of my javascript related posts from here on out. Too many people are using inline attributes in the markup to trigger Javascript these days. It's undoubtedly wiser to do it the unobtrusive way for many reasons. The script degrades gracefully, will be easier to maintain, and will further separate behavioral logic from markup. All you have to do is bring javascript file into the markup (with <script> tags in the <head> section) and watch it work. If you want to learn more about unobtrusive javascript and its benefits, see the wonderful List Apart article by Jeremy Keith.
 
I hope somebody finds this useful!
                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74: