http://www.icefaces.org/JForum/posts/list/4616.page

Any hope of this being fixed (or even assigned) anytime in the next two years? This is a serious issue.

Yes, I agree. This problem is causing us siginificant issue with the field techs who use our software. We are getting a lot of complaints and need a fix.

I totally agree with Jason and Barbara, this issue is open for over two years! , I'm working with version 1.8.1 and this issue occurs again and again, we need this to be solved, please

Also, the scroll position should be settable from server-side code, since the app may want (for example) to position the list to a particular area when it is first displayed.

The scroll position on components seem to work but ONLY after the first submit on a page.

For example, if you have a <ice:panelGroup scrollHeight="200px"> on a page, and a <ice:selectInputDate , when you first select a date, the panel group will reset to the top. If you select a data again, and all subsequent selections, the panel group scroll position works flawlessly (even after rescrolling). You can click other components, commandbuttons, etc, all work perfectly, but it must be after the first action before things work.

I am using icefaces EE 2.0 with Mojarra 2.1.1 (I also tried 2.1.3)

One thing I did noticed is that after selecting a date the first time, this is printed to the console:
[window] append missing "javax.faces.ViewState" input element to form["vsxko5ij"]

Should no view state yet exist for the components on first load, how can the scroll position be maintained?

Ultimately this CAN be fixed and MUST be fixed. I share the same sentiment as other developers. I know a lot of effort is being put into icefaces - but it is important that attention to detail on things like this take top priority. Otherwise these components don't have much value.

Introduced 'scrollPosition' binding that can be used to preserve the scroll position after a page reload. The scroll position is sent 400ms after the scrolling has stopped. When the page is loaded the script element inserted by the TableRenderer will reset scrolling position to where it was previously.
The'scrollPosition' binding needs to be done to a bean that survives a page reload, such as 'window' scope.