Link to home
Start Free TrialLog in
Avatar of JOHNFROG
JOHNFROG

asked on

Maintaining scroll position (using nested masterpages) on clicking ajax tabContainer

For some reason, introducing an AJAX TabContainer with multiple Tabs forces the scroll position to return to 'just below' the top every time a tab panel is changed.

I have exhausted my patience on trying to implement the solution described here
http://weblogs.asp.net/andrewfrederick/archive/2008/03/04/maintain-scroll-position-after-asynchronous-postback.aspx

I assume its got something to do with using nested masterpages. All examples only extend to simple masterpages.

Have the following in my web.config
<pages maintainScrollPositionOnPostBack="true"> blah blah..................
</pages>

Seriously thinking of abandoning tabContainers as have had numerous issues so please help.
ASKER CERTIFIED SOLUTION
Avatar of xav056
xav056

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Eduardo Goicovich
Eduardo Goicovich
Flag of Chile image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of JOHNFROG
JOHNFROG

ASKER

have tried removing maintainScrollPositionOnPostBack="true">
from web.config but still cannot maintain scroll position on tab change.

It is worth noting that if I simply refresh the page using F5 then the page WILL return to the last scroll position.

Every other AJAX control does not have this problem unless a tabContainer is on the page.

For instance, I placed a simple radio button on the bottom of the page below the TabContainer with auto postback turned on. When I change the value of the radiobutton it also returns scroll to the top.

Now if I take away the entire TabContainer and add a bunch of </br>'s to take it place but change nothing else, then the changing of the same radiobutton will maintain scroll position.

Any further help will be appreciated and tested but I have already started building my own tab container using buttons and panels. This has its benefits already as I can easily add some ajax animations etc. More flexibility but messy as.

using google chrome
Ahhhh. Just tested on Firefox and position was maintained.

Any chrome specific patches?
retiring this question due to the browser issue becoming relevant.