Difference between rendered and visible attributes of

by

The rendered attribute is server-side and the visible attribute is client-side. The rendered attribute tells whether JSF should generate the dialog’s HTML representation or not. The visible attribute tells whether HTML/CSS/JS should immediately show the dialog on browser’s page load or not.

If the dialog isn’t rendered, then you won’t be able to display it by for example JavaScript dialogWidgetVar.show() without reloading the page or ajax-updating one of the dialog’s parent components that way so that the dialog’s rendered condition evaluates to true. Also the visible attribute won’t have any effect if the dialog is not rendered simply because there’s nothing being rendered to the resulting HTML output which could be shown/hidden by JavaScript.

If the dialog is rendered, then it is by default hidden. You can set visible to true to force it to display the dialog immediately whenever the page is opened. Or you can invoke JavaScript dialogWidgetVar.show() in some onclick or oncomplete attribute to show it.

Use the rendered attribute if you don’t want to render the dialog at all, for example because it wouldn’t ever be used anyway in the currently requested page composition.

More Related Contents:

  1. How to use PrimeFaces p:fileUpload? Listener method is never invoked or UploadedFile is null / throws an error / not usable
  2. Real time updates from database using JSF/Java EE
  3. Unicode input retrieved via PrimeFaces input components become corrupted
  4. How to show details of current row from p:dataTable in a p:dialog and update after save
  5. p:commandbutton action doesn’t work inside p:dialog
  6. PrimeFaces CSS look’n’feel missing and JS “Uncaught Reference Error: PrimeFaces is not defined”
  7. Display database blob images in inside
  8. Execution order of events when pressing PrimeFaces p:commandButton
  9. Showing Hibernate/JPA results in JSF datatable causes: java.lang.NumberFormatException: For input string: “[propertyname]”
  10. @ViewScoped bean recreated on every postback request when using JSF 2.2
  11. PrimeFaces validator not fired
  12. Naming Container in JSF2/PrimeFaces [duplicate]
  13. PrimeFaces CSS skin not showing in login page, also JavaScript undefined errors
  14. Using a “Please select” f:selectItem with null/empty value inside a p:selectOneMenu
  15. h:messages does not display messages when p:commandButton is pressed
  16. How to write a custom converter for
  17. p:dataExporter does not recognize p:cellEditor
  18. Customize primefaces chart
  19. JSF + PrimeFaces: `update` attribute does not update component
  20. PrimeFaces commandButton doesn’t navigate or update
  21. UISelectMany on a List causes java.lang.ClassCastException: java.lang.String cannot be cast to T
  22. p:commandButton vs. h:commandButton
  23. Reset input fields without executing validation
  24. p:selectOneMenu dropdown part scrolls and does not stay in position
  25. c:forEach inside primefaces(e.g. p:panelgrid) inside ui:repeat
  26. Primefaces valueChangeListener or
  27. Store PDF for a limited time on app server and make it available for download
  28. Remove all styling from Primefaces components?
  29. LazyInitializationException in selectManyCheckbox on @ManyToMany(fetch=LAZY)
  30. JSF resource versioning

Leave a Comment