Skip to main content

Fields are cleared but just when I press F5



I don't know if it is a common problem, but this strange problem is giving me some headache... I'm having an strange behavior, my application has a lot of dialogs, and when user opens one, the dialog should show default content. The problem is that I clear all bean's properties before show the dialog, but sometimes it appears that the form isn't cleared!! For example, this is one of the dialogs that are having this problem:





how it should be This image show how the dialog appears the first time I open it, all fields are cleared and the second radio is selected. If I change the radio selection and enter something in the input field, the datatable immediately shows the data accordingly with the search. So, if I click in "Cancelar" (cancel in portuguese), this dialog is closed, like expected.





Then I open this dialog again and:





how it is shown after oppened after cancel action The fields store the last edition user made. I thought I wasn't clearing the bean, but if I just press F5 (refresh) the dialog is shown like in the first image. I don't know why, but some fields aren't updated!!





My dialogs are created using this template:







<ui:component>

<hrgi:popup id="#{idPopup}" titulo="#{titulo}" renderizar="#{popup.visivel}"

bordaConteudo="#{bordaConteudo eq null?true:bordaConteudo}">

<f:facet name="cabecalho">

<ui:insert name="cabecalho"></ui:insert>

</f:facet>

<f:facet name="conteudo">

<h:panelGroup id="#{idPopup}Conteudo" layout="block" style="width:100%">

<p:focus/>

<ui:insert name="conteudo">Nenhum conteúdo definido!</ui:insert>

</h:panelGroup>

</f:facet>

<f:facet name="botoes">

<h:panelGroup style="width:100%">

<h:panelGrid id="#{idPopup}PainelMensagens" style="width:100%">

<p:messages/>

</h:panelGrid>

<ui:insert name="barraDeBotoes">

<h:panelGroup layout="block" style="width:100%">

<p:commandButton value="CANCELAR" styleClass="hrgi-botao-popup"

immediate="true" update="@form"

action="#{controladorPopup.fechar}"/>

<p:commandButton value="OK" styleClass="hrgi-botao-popup"

action="#{controladorPopup.submit}" update="@form alerta #{atualizar}">

<f:param name="REQUIRED" value="true"/>

</p:commandButton>

</h:panelGroup>

</ui:insert>

</h:panelGroup>

</f:facet>

</hrgi:popup>

</ui:component>







is my own dialog component...





Could someone explain me why it is happening??


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex