Modify

Ticket #279 (new defect)

Opened 2 years ago

Caching of selection-control + dblselect-control in IE

Reported by: sdm Owned by: mpo
Priority: major Milestone: 0.5
Component: modules/kauri-forms Version: trunk
Keywords: Cc:

Description

In IE, the values of a selection-control and a dblselect-control are cached.
Example of this behaviour:

An application has 2 web pages A and B. Page A allows CRUD on user objects. Page B shows a list of user objects in a selection-control.
First, go to page B => the user selection-control is filled with the current list of users. Then, go to page A and create a new user. Go back to page B: the new user is not added to the selection-control, not even if you refresh the page or if you click the "refresh" icon from the selection-control itself.
The only thing that helps to make the selection-control always show the current list of users, is to put the following code on page B:

$.ajaxSetup( {
   cache: false
});

This piece of code adds a random value to the URL that fetches the list of users.

Maybe it would be a good idea to add a similar "cache": true/false option to the Kauri selection-control and dblselect-control?

Attachments

View

Add a comment

Modify Ticket

Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.