_isAutocompleteDisabled :  function (element) {
        if (element && element.hasAttribute("autocomplete") &&
            element.getAttribute("autocomplete").toLowerCase() == "off")
            /** Change this line to be return false **/
            return false;

        return false;
    },

Firefox sees various values differently on the main screen and on the secondary screen… here is a quick table with the info — for reference sake, the secondary display is vertically positioned above the primary display, and my Dock is on the left side of the primary screen…

So, you’d think the same script would work fine… but on the primary screen, moving to (0,0) put you at (availTop, availLeft), aka (22,53) because of the Dock and the OSX menu.

The code that worked for me…

resizeTo( 1024, screen.availHeight );
var screenTop = screen.availTop;
if( screen.availHeight != screen.height ) {
    screenTop = 0;
}
moveTo( screen.availLeft, screenTop );

resizeTo( 1024, screen.availHeight );
moveTo( (screen.availWidth - 1024), 0 );


For some reason though, Firefox has always had some strange behavior when running this script on my systems with multiple monitors.

When on the second display, the window will resize itself properly, but will not position itself according to the math above.  Even inspecting the availWidth field turns out what I’d expect…

I finally figured out why. The moveTo method doesn’t work on the same origin point as the availWidth fields. The important javascript properties that I need to know about are the screen.availLeft and screen.availTop.

In Firefox…  When multiple monitors are positioned side-by-side, availLeft on the left monitor will be zero, and on the right monitor it will be 1024 (or whatever the width resolution is on monitor on the left).  When there is only one screen, availLeft will be zero.

When multiple monitors are stacked vertically, availLeft will be zero on both monitors, and availTop will be zero on your main monitor (the one with the windows task bar) and will be -768 on the other monitor.  This is inconsistent with the availLeft behavior, but once we know about it, it is easy to work around.

So now, my start page script has the following code:

resizeTo( 1024, screen.availHeight );
moveTo( screen.availLeft + (screen.availWidth - 1024), 0 );

When on a single screen, availLeft is zero, and doesn’t affect the calculation.  When on a multi-screen display, it will position the browser as I desire, regardless of which screen the browser is on.

Updated April 08: Also see my follow-up post on OSX + Javascript + Multiple Monitors.

http://www.java2s.com/Code/JavaScript/CatalogJavaScript.htm

As you might imagine, there are examples for more things in the entire website…

http://java2s.com/

     if( expandedAccountSummaryLayer )
     {
       expandedAccountSummaryLayer = false;
	if (agt.indexOf('msie') != -1) {
 	       theButton.childNodes[0].src = imgpath + "/expandButton.gif";
        } else {
 	       theButton.childNodes[1].src = imgpath + "/expandButton.gif";
        }
       if ( theLayer != null ) {
         theLayer.style.height = "138";
         theLayer.style.overflow = "auto";
       }
     }
     else
     {
       expandedAccountSummaryLayer = true;
	if (agt.indexOf('msie') != -1) {
 	      	theButton.childNodes[0].src = imgpath + "/collapseButton.gif";
        } else {
 	      	theButton.childNodes[1].src = imgpath + "/collapseButton.gif";
        }
       if ( theLayer != null ) {
         theLayer.style.height = "auto";
         theLayer.style.overflow = "auto";
       }
     }

function blockEnter(evt) {
    evt = (evt) ? evt : event;
    var charCode = (evt.charCode) ? evt.charCode :
          ((evt.which) ? evt.which : evt.keyCode);
    if (charCode == 13) {
        return false;
    } else {
        return true;
    }
}
<input onkeydown="return blockEnter(event);" name="search" size="40" type="text" />

This post is password protected. To view it please enter your password below:

Password: