JavaScript/IFrame/Form woes.

Hey Jim, thanks for the response. I've tried the forms[0].elements[0].value syntax and never gotten a result. I tried using your code and got 'ifDoc.forms[0] has no properties' in my error console. I also stuck an alert(ifDoc.forms[0].elements[0].value) as a test and it didn't get executed. Any idea why that is?

Hmm... could it be something like greasemonkey isn't set to run on the site in question? I did all the work using Firebug, so that may be a source of deviations. Maybe poke around in its settings? Also, try going up a level and doing the alert, until you get one that's set. So do alert(ifDoc.forms[0].elements[0]); then alert(ifDoc.forms[0]); then alert(ifDoc) etc. until you find one that isn't empty. You might also check the lengths of the various arrays.

It may have something to do with how firefox loads the iframe. It looks kind of like the frame doesn't actually load until the greasemonkey script ends, so it could be that Firefox loads the iframe content synchronously. Since the document hasn't loaded, it doesn't have any forms yet.

can't do anything spiffy with AJAX or modify the form somehow, because it's hosted/controlled by another entity Huh? If the form is ever loaded in your browser, you control the form, or at least that local copy of it. Your script can extract any value out of there, change a selection as would happen manually, and resubmit to the controlling entity without the entity being any the wiser. A submitted form isn't going to an Evil Form Minder which interrogates the browser to ensure there was no nefarious JavaScript code automating the process. Absent further restrictions (e.g. running in a Java applet), it sounds like you might be making things overcomplicated and causing yourself unnecessary grief. I'm unclear on why the following scenario doesn't work: Go to the form URL as you would for manual input. Have a GM script for that page pick your topmost ID number and submit the number via the URL by changing window.location.href. The form loads for that ID number. Your GM script activates again on the new form load, modifies the drop down to your desired value, and triggers the update. Form goes to a"thank you very much page" or whatever it normally does. GM script activates on page load again to navigate back to the original form URL, submits the next ID number, rinse and repeat. All the script need do across page loads is track the remaining list of IDs and where you are in the process, i.e. the phase of the ID submission, which it can do via the local GM/browser store. The script can hold the ID list or, since there are a lot of numbers, you could have the script read the ID list from a web page or web-readable e-mail. Then local store need only track the index of the last submitted number on the list. I don't see anything special about your iframe that couldn't be done easier directly on the page, bypassing all the explicit frame reference hoodoo. Avoid shoehorning in another frame to add to the headache unless there's a real need for it. This process sounds, at least to me right now, like a basic automation task that GM is well-equipped to manage.