YES, thank you! That worked with one minor problem: I see the value I am setting being put into the field, but it's immediately erased (it flashes and is erased), because the page erases all fields when the it first loads. It seems that my script runs first, then the field cleanup code runs. I can either wait a while and then run my script, or somehow find out the code that cleans up the fields and prevent it from running (not sure how to do this, though).
So, further suggestions would be welcome! ;-) On Jun 10, 7:23 pm, John5342 <[email protected]> wrote: > On Thu, Jun 10, 2010 at 14:24, Toddintr <[email protected]> wrote: > > I also found out the following: > > > var x=document.getElementsByName('textMARS'); > > alert(x.length); > > > The above code prints out "1", so I know that the element is being > > found. However: > > > x.value="1234567'; > > > does not work. > > x is a collection of nodes rather than the node itself. Perhaps x[0].value ? > > -- > There are 10 kinds of people in the world: Those who understand binary > and those who don't... -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
