Hi Matt, Do you have any code that you could show us? My first instinct would be that it may have something to do with an invoker you are using to handle the event. By default, invokers now cache their values, unless you provide the "dynamic: true" flag to their configuration.
As for venue, it's fine to ask questions here, but you can also ask on the Infusion-Users list. Thanks Justin On Jun 24, 2014, at 6:22 PM, Matt Polizzotti <mpolizzo...@unicon.net> wrote: > Hello Everyone, > > Please let me know if this is not the correct venue to ask a question about > the fluid pager. > > The uPortal community has recently upgraded from fluid 1.4 to 1.5 and we have > an implementation of the fluid pager that leverages the onModelChange event. > When the onModelChange event fires some work is performed on the pager's > underlying list items. After upgrading we noticed that the DOM references to > the list items became stale within the context of the onModelChange handler. > I cannot be absolutely certain that upgrading caused this issue but I wanted > to ask the group if what I have described should be working? Should we be > able to access an updated DOM within the context of an onModelChange handler? > Or are we using the wrong pager event? Please let me know if additional > details are needed. > > Any help would be appreciated. > > Thank you, > Matt Polizzotti > _______________________________________________________ > fluid-work mailing list - fluid-work@fluidproject.org > To unsubscribe, change settings or access archives, > see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
_______________________________________________________ fluid-work mailing list - fluid-work@fluidproject.org To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
