When the page is first loaded, the mouse can't be used to set the focus to one of the textbox controls. What I've noticed is that any control that isn't positioned "on top" of the goDiagram object can have focus set to it with a mouse click. Anything positioned "on top" can't be clicked into. A user can tab into it, but not click into it. Positioning the godiagram off of the page, enables all of the textbox controls to be clicked.
This leads me to believe that something about the godiagram is trapping the mouse clicks.
Here's where it get's even stranger, if, after page load, I tab to the 2nd tab (with the godiagram on it) and then back to the first tab, all controls can be clicked.
Any idea what might be trapping the mouse actions immediately after a page load? I put an alert on the doMouseMove in goweb.js, and it doesn't fire unless I have the godiagram positioned on the first tab, or I tab over to the 2nd tab. So, I can't explicitly make the mouse events be trapped. I even tried commenting out the
Hopefully that ramble made sense. Ever run across anything like this before? My last hope is to position the godiagram object off of the page, until the tab is selected and then position it back to the usable location.
Thanks for any help you can provide.