Yuk. That didn't happen in the local mock up I made from your previous page (the one I sent you some time back as glidermap.zip) remember it?
Anyways, one difference is in the css for the glidecontentwrapper class. On the current page it's set to 1150px. Try changing that to 850px. That's in the featuredcontentglider.css file.
The browser cache may need to be cleared and/or the page refreshed to see changes.
It might be something else, or that and something else. Give that a shot:
No it's just that. I since tested it and that fixes it. I also noticed that there's no cache busting on the import of the external calgaryNEcontent.htm file. That means that if you change that file, in some browsers a returning visitor will still see the old version.
/* CSS Document */
position: relative; /* Do not change this value */
height: 850px; /* Set height to be able to contain height of largest content shown*/
Total wrapper width: 350px+5px+5px=360px
Or width of wrapp . . .
You can fix that by adding to the on page init:
gliderid: "calgaryneproperties", //ID of main glider container
contentclass: "glidecontent", //Shared CSS class name of each glider content
togglerid: "p-select", //ID of toggler container
remotecontent: "calgaryNEcontent.htm?bust="+new Date().getTime(), //Get gliding contents from external file on server? "filename" or "" to disable
selected: 0, //Default selected content index (0=1st)
persiststate: false, //Remember last content shown within browser session (true/false)?
speed: 500, //Glide animation duration (in milliseconds)
direction: "downup", //set direction of glide: "updown", "downup", "leftright", or "rightleft"
autorotate: false, //Auto rotate contents (true/false)?
autorotateconfig: [3000, 2] //if auto rotate enabled, set [milliseconds_btw_rotations, cycles_before_stopping]