It would be great to get some help from JS gurus.
In this file of OERP v.7:
... we have the following nice comment:
// FIXME: ignominious hacks, parents (aka form view) should not send two ListView#reload_content concurrently
The comment has even successfully made it into the trunk of OERP v.8.
As I only have very little experience with JS, I've spent half a day trying to spot this second invocation -- all in no avail.
Would anybody be so kind as to point me to the exact place where this second invocation of reload_content is happening in the given function (render_dataset)? And probably even somewhere outside of it...
I do see it happening in the web UI, but ridiculously cannot spot it in the source code. Namely, in my (search) wizard, when I press the 'Search' button, the page is quickly reloaded with the results of previous search on it. And only upon receiving the new results of the new search the page is reloaded again with the correct/updated results on it.
So, basically, I'd like to get rid of that initial reload with old data, which creates an impression that the search wizard has returned the very same data. And yes, I tend to suspect exactly this portion of JS-code in causing this strange behavior.
Any help would be highly appeciated,
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 1/13/14, 2:07 PM|
|Seen: 1033 times|
|Last updated: 3/16/15, 8:10 AM|