If you encounter browser specific issues, then there's most likely a bug in the generated or homegrown JavaScript or CSS used. All JSF does is generating and sending HTML/CSS/JS and all the webbrowser retrieve and understand is HTML/CSS/JS.
If you encounter a bug in the generated HTML/CSS/JS (which is very rare though), which is not fixed yet in the latest JSF implementation version, then best what you can do is to report it to the JSF impl boys. At least, Mojarra boys are known to prioritize client side issues very high. Last serious issue I recall with regard to Mojarra is a Safari/Webkit related bug with document.forms[formname]
, but that's already been fixed over 2 years ago.
Coming back to problems specifically with rendered
, disabled
and readonly
attributes: those are also often caused by not properly understanding the lifecycle of HTTP request/response (the request scope) and/or the JSF lifecycle (those attributes are also checked during apply request values) and/or the wall between client side and server side (you cannot change them with alone JavaScript without sending/handling as HTTP request parameter yourself). This is unrelated to webbrowsers.