[richfaces-issues] [JBoss JIRA] (RF-13435) extendedatatable: Scrolling position is lost after submit

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938444#comment-12938444 ] 

Brian Leathem commented on RF-13435:
------------------------------------

The fix to this would be to add a {{rich:ready}} jQuery listener to set the scroll value.  If someone wants to develop this as a workaround and post the details here, we could include it into the extendeddtatable.js as a patch.
                
> 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
>              Labels: extendeddatatable, richfaces, scroll
>             Fix For: 5-Tracking
>
>
> 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