]
andreas_back updated RF-4431:
-----------------------------
Attachment: filter.zip
The file filter.zip shows the stream content of the conversation between the
client and the server and reports the reloadings.
For example the string
<input id="formDataTable:dataList:14546:Input1" type="text"
name="formDataTable:dataList:14546:Input1" value="4003801055299"
appears serveral times within the log file in different ajax responses
for the reaction to one scrolling interaction.
This might indicate a loop.
EndlessLoop for Columns in ScrollableDataTable
-----------------------------------------------
Key: RF-4431
URL:
https://jira.jboss.org/jira/browse/RF-4431
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: Firefox 3.0.1
Reporter: andreas_back
Assignee: Konstantin Mishin
Fix For: 3.3.0
Attachments: filter.zip
If the Firefox 3.0.1 browser is used to scroll within a rich:scrollableDataTable
that uses rich:columns then the table shows some oszillating behaviour:
The table issues repeatingly requests to the server and it does so for
more than ten minutes if the browser is not terminated.
This behaviour has been observed for
* richfaces-ui-3.2.2.CR4 and back to
* richfaces-ui-3.2.2-20080702.044834-27
You can find a war-Archive with an example application under the following url:
http://www.intermoves.de/fileadmin/richfaces/ListenValidator.war
The war-Archive was build with JDK 1.6.0_02 and has been tested with
apache-tomcat-6.0.16.
A zip-Archive with an eclipse 3.2.2 project (for Windows XP) can be found under this
url:
http://www.intermoves.de/fileadmin/richfaces/ListenValidator.zip
For a local deployment the URL of the application in the war archive is
http://localhost:8080/ListenValidator
Remark:
Under Safari 3.1.2 (525.21) it is not possible to move the
scrollbar to the bottom of the table in one scrolling, the scrolling bar
pauses several times. But if you try serveral times the bottom lines
of the table can be reached.
It would be great if these points could be fixed for the 3.2.2 GA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: