Modify ↓
Opened 17 years ago
Closed 17 years ago
#4 closed defect (fixed)
Firefox refresh problem
Reported by: | clolas | Owned by: | dkart |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | component1 | Version: | 1.0 |
Keywords: | HMI, Firefox, webif | Cc: |
Description
Temperature setpoint selection is not updated upon page refresh in Firefox browser.
Attachments (0)
Change History (5)
comment:1 Changed 17 years ago by anonymous
- Keywords webif added
comment:2 Changed 17 years ago by anonymous
- Owner changed from dkart to anonymous
- Status changed from new to assigned
comment:3 Changed 17 years ago by dkart
- Owner changed from anonymous to dkart
- Status changed from assigned to new
comment:4 Changed 17 years ago by dkart
- Status changed from new to assigned
comment:5 Changed 17 years ago by dkart
- Resolution set to fixed
- Status changed from assigned to closed
This defect has been fixed with the use of some itchy bitchy javascript (see revisions 6540, 6544, and 6545)
Note: See
TracTickets for help on using
tickets.
Found this post on the web; it may provide a solution to this problem:
Michael J. Hudson 27-Sep-2006 07:12 There has been some discussion on the best way to FORCE a refresh of a page. In general, the solutions revolve on reducing or eliminating caching. However, I think that what some people are looking for... is how does one force a real refresh of the page after some internal action on the page (be it a javascript action OR a button was pressed). I found the following code VERY helpful when I encountered this need. Specifically, I had a listbox where one could press a button to delete a selected entry in that listbox. The listbox was dynamically linked to the contents of an external source only in the sense that the listbox got updated with the current list ONLY when the page got refreshed. Thus, I needed a way to force a refresh after the person pressed the delete button. I did this by adding the following code after my actual delete action.
Do note, the above code is written to be VERY generic. You can probably simplify it greatly if the port is a standard port and/or you are always using http or https and/or you don't expect to have a query string appended to the end.
BTW, I didn't come up this code myself... I happened across it while reading the following article on auto-login techniques for Mediawiki: http://meta.wikimedia.org/wiki/ User:Otheus/Auto_Login_via_REMOTE_USER/code