Holger Walter created RF-13435:
----------------------------------
Summary: extendedatatable: Scrolling position is lost after submit
Key: RF-13435
URL: https://issues.jboss.org/browse/RF-13435
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.3.4
Environment: ALL
Reporter: Holger Walter
Issue is similar to RF-5312.
In EDT, the current scrolling position is lost (reset to 0) after a submit.
Steps to reproduce:
1. Use the showcase for the EDT(version 4.3.4)
2. Adapt the xhtml file by adding a simple submit button ( <h:commandButton
value="Submit" />)
3. Activate the 'ajax loading' checkbox
4. Scroll down in the table
5. Press the new submit button
6. The scrolling position is lost
This might sound as a minor problem, but in case of using the EDT with ajax
data loading, a user can scroll quite far until he may find the row on which he
wants to do some actions. If the scrolling position is reset to 0 after each
submit, it gets quite tedious for a user scrolling every time to this old
position in the table.
I've seen that the current position is already stored in componentState, but
unfortunately it is getting reset on submit.
I already tried a workaround, by using the 'onready' event of the EDT after a
submit to trigger scrolling to the desired position with javascript but this
does not work reliably on one hand, and triggers an additional ajax call which
may cause that messages in h:messages are lost.
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
