• Post Reply Bookmark Topic Watch Topic
  • New Topic

refresh problem in Firefox

 
srilakshmi madala
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
using JSF framework. when you select one drop down value and click on refresh before submit the initial value got selected in chrome and IE
But getting issue in firefox. The initial value is not populating.
With the text box also the same issue. when we enter something and refresh before submit values are not refreshing in Firefox
 
srilakshmi madala
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
srilakshmi madala wrote:using JSF framework. when you select one drop down value and click on refresh before submit the initial value got selected in chrome and IE
But getting issue in firefox. The initial value is not populating.
With the text box also the same issue. when we enter something and refresh before submit values are not refreshing in Firefox


Can you please help on this .
 
Tim Holloway
Bartender
Posts: 18408
58
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Patience! When you get a service for free, you must expect that instant service is probably not going to be a feature you can expect.

I'm not sure what you mean by "click on refresh". If you are referring to the Page Reload function that happens in most browsers when you press the F5 button or click on a related item on the toolbar, the Page Reload re-submits the last page URL to the server. What displays is then going to be determined by the server. In the case of JSF, that means that any changes made to the page since it was originally loaded will be lost (assuming no AJAX or meta-data induced updates were posted since then). The page would then be re-rendered by the JSF lifecycle processor according to the current values of its model(s) (backing beans).

This process is not browser-specific, so whatever browser you use should achieve the same results. However, if the "refresh" button isn't a "reload" button, I can't predict what would happen.
 
srilakshmi madala
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim Holloway wrote:Patience! When you get a service for free, you must expect that instant service is probably not going to be a feature you can expect.

I'm not sure what you mean by "click on refresh". If you are referring to the Page Reload function that happens in most browsers when you press the F5 button or click on a related item on the toolbar, the Page Reload re-submits the last page URL to the server. What displays is then going to be determined by the server. In the case of JSF, that means that any changes made to the page since it was originally loaded will be lost (assuming no AJAX or meta-data induced updates were posted since then). The page would then be re-rendered by the JSF lifecycle processor according to the current values of its model(s) (backing beans).

This process is not browser-specific, so whatever browser you use should achieve the same results. However, if the "refresh" button isn't a "reload" button, I can't predict what would happen.



The page would then be re-rendered by the JSF lifecycle processor according to the current values of its model(s) (backing beans).
I got you. But here the issue was it is browser specific. it is not getting the current values from the backing bean. When ever we select value from the drop down it is going to store in firefox cache. But is not happening in chrome.
I tried with automcomplete ="off" but is not working for drop down values. What ever you explained above i got everything. One more thing i am not in a hurry. I forgot to mention that sentence above That is the reason i posed that later.
Thanks for understanding
 
Tim Holloway
Bartender
Posts: 18408
58
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just take it as a given that if you ask a question here, you're looking for help. :)

Now that I think of it, there's an HTML option on the Button control for "reset". If you put a reset button on the form and click it, then the browser will reset all the form control values to whatever they were when the page was initially rendered. The HTML reset control - and its JSF counterpart do not contact the server to do this.

The reload feature, however, explicitly does resend the last URL page request to the server. To JSF, that looks exactly like any other page request and the normal JSF lifecyle processing is done. JSF neither knows nor cares what brand or version of browser has made the request.

One thing that can cause trouble is if your backing bean is a request-scope bean. Request scope is almost entirely useless in JSF. However, I don't know of any case where mis-use of request scope should be causing browser-specific problems. It should misbehave equally on all of them.
 
srilakshmi madala
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim Holloway wrote:I just take it as a given that if you ask a question here, you're looking for help. :)

Now that I think of it, there's an HTML option on the Button control for "reset". If you put a reset button on the form and click it, then the browser will reset all the form control values to whatever they were when the page was initially rendered. The HTML reset control - and its JSF counterpart do not contact the server to do this.

The reload feature, however, explicitly does resend the last URL page request to the server. To JSF, that looks exactly like any other page request and the normal JSF lifecyle processing is done. JSF neither knows nor cares what brand or version of browser has made the request.

One thing that can cause trouble is if your backing bean is a request-scope bean. Request scope is almost entirely useless in JSF. However, I don't know of any case where mis-use of request scope should be causing browser-specific problems. It should misbehave equally on all of them.



firefox is behaving differently from chrome and IE. I tried to reset the values . But no use. The change should be from UI side . Not from any where that is what i am thinking. if you have any tag in jsf please let me. Thank you very much for your suggestions and explanation..
Thank you so much for spending time on this
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!