Bug? calling javascript click() on a hidden button causes js error on page

Question

I call the .click() method on a hidden button to cause the page to refresh. This works OK, but when the page comes back up, it has a javascript error on it. It turns out the error is from some javascript that is trying to set the focus on the hidden button that was clicked, which causes an error in IE (This doesn't seem to bother Firefox) .
While I imagine that there are workarounds, why should the underlying faces architecture be setting the focus to a hidden button?
It's easy to duplicate:
Create new page. Add two buttons. For the first, make it invisible (uncheck visible in properties), then cause it to submit a virtual form.
For the second, add this to the onclick:
document.getElementById("form1:button1").click();return false;
Bring up the page, click on the visible button. The page will refresh, and you'll have a nice js error.
BTW: Obviously, I don't want to click one button from another. What I want is a way to cause an action to happen from javascript. I can't imagine it would work to simply submit a form from javascript, so I use this method. It works fine except for the error. Is there a better way to do this?

Answer 1

which causes an error in IE (This doesn't seem to bother Firefox) .Vaious browsers behave differently at times when executing javascript code. Many instances of this can be found on the net. This is a browser specific problem.So it's ok to set the focus to a hidden button because firefox is more relaxed about this obvious error than explorer is? When would anyone really want a hidden button to gain focus? What do I tell my users--don't use explorer, because it doesn't like it when faces sets the focus to a hidden button? Ignore the error message you get? What?
BTW: Obviously, I don't want to click one button from another. >>What I want is a way to cause an action to happen from javascript.Please describe in detail what action you would like to perform from javascript. It is not clear as to what the use case is.
I don't really see how the use case matters. I gave a very easy example how to duplicate this problem. The reason that I want to do this is that there are many places to enter javascript code that don't allow for an action to be triggered. I have many instances of this. For example, I'd like a mouseover on an edit field to cause an action. I can capture this in javascript, but I can't cause any server side processing. To get around this limitation, I call the hidden button's .click method, which does cause a server side event.
Here's a simpler, more direct incarnation of this error that doesn't involve javascript.
Create a new page. Put an element on it, like an edit box. Put a button on the page. For its action, put:
public String button1_action() {
getButton1().setVisible(false);
return null;
Pressing this button will cause a page refresh, and then a javascript error.
Use Case: After the user presses the button, they shouldn't be allowed to press or see it again.