Using a4j: commandbutton vs h: commandbutton to present new pages in richfaces

Question

I completely replaced h: commandButton with a4j: commandLink in my application for reasons unrelated to this problem. Since then, I have seen unusual side effects in IE8, such as selection menus, that lose focus and select items that cannot be selected.

Does anyone think it is a bad idea to use a4j: commandButton instead of h: commandButton for some reason? Does anyone have any previous experience?

Any answer is welcome.

Answer 1

Look at here:

http://community.jboss.org/wiki/CommonAjaxRequestsProblems#navigation

Answer 2

There is a problem when using a4j:commandLink to navigate in Firefox 3.5, as described here

JSF issue with FireFox 3.5 caching, wyciwyg: // prefix