[
https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s...
]
Holger Walter commented on RF-13615:
------------------------------------
Hi Brian,
thanks for the feedback. Just tried to debug the client as described in your link.
Unfortunately <a4j:log/> (RF 4.3.6) does not work in Firefox 28.
Get the message 'Richfaces.HtmlLog()' is not a constructor'.
In IE10 <a4j:log/> works.
I did some debugging regarding the 2nd ajax request. I'm not really sure, but I think
the function 'setColumnWidth' in extendedDataTable.js is the problem. It always
sends ajax requests in case it is called (last line in function) - and it will always ( on
each other request) be called after the width of a col has changed.
Hope you can check this.
Regards
wlh
ExtendedDataTable: double ajax request on scrolling
---------------------------------------------------
Key: RF-13615
URL:
https://issues.jboss.org/browse/RF-13615
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: showcase
Affects Versions: 4.3.6
Environment: Problem can be tested in richfaces showcase.
http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende...
Reporter: Holger Walter
1. Go to the extendedDataTable showcase
2. Turn on ajax loading.
3. Open the debugger of your browser and watch the network communication
4. Scroll down in the table untli new data has to be fetched.
=> one POST request is sent. This is fine.
5. Change the width of a column in the table.
=> one POST request is sent. This is fine.
6. Scroll again in the table untli new data has to be fetched.
-> 2 POST requests are sent. WHY?
From now on, on each scroll, the table always sends 2 requests. This behavior stops only
when your relaod the table.
Due to this behavior I get some perfromance issues, as I have to execute some own
javascript after each request.
Is there a possibility to prevent the 2nd POST request. I would be happy even with a
dirty hack, or just a hint showing me from where the 2nd request is triggered.
Best regards
wlh
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira