Welcome Guest Search | Active Topics | Sign In | Register

eo:CallbackPanel vs WebForm_DoCallback Options
bobwolf
Posted: Friday, March 6, 2009 2:09:27 PM
Rank: Member
Groups: Member

Joined: 5/31/2008
Posts: 25
Hi guys,

I have some pages that I use "WebForm_DoCallback" from .Net.
In one of that pages I have implement the eo:CallbackPanel and my WebForm_DoCallback has stopped working.

Do you know if there are any known issues about using "eo:CallbackPanel" and "WebForm_DoCallback" in same page?


tks
bob.
eo_support
Posted: Friday, March 6, 2009 3:07:47 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

We are not aware of any issues regarding this. If you can create a test page that reproduces the problem, we will be happy to take a look and see what we can find.

Thanks!
bobwolf
Posted: Saturday, March 7, 2009 10:51:58 AM
Rank: Member
Groups: Member

Joined: 5/31/2008
Posts: 25
Tks for reply!

Now i'm trying to remove the DoCallBack, and using only the eo:CallBackPanel.
I thing that will be a simply way!

Tks again.

Regards
bob.
eo_support
Posted: Saturday, March 7, 2009 11:09:14 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hopefully. :) Let us know if you still have problems.
bobwolf
Posted: Monday, March 9, 2009 8:55:11 AM
Rank: Member
Groups: Member

Joined: 5/31/2008
Posts: 25
Hi guys!
The work is almost done!
=)

bob.
eo_support
Posted: Monday, March 9, 2009 9:06:03 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

CallbackPanel does not touch scroll position. However if you use CallbackPanel to update the whole page, or a large portion of the page, then this can happen because the first step of the CallbackPanel is to "remove" the old contents. When that occurs, the page shrinks to nothing and the browser automatically scroll to the top because scrolling is no longer needed. The workaround for this scenario is to make sure you have other contents in the page that would prevent the page to shrink during callback.

Another scenario this can happen is that you have custom code that manipulates scrolling position. That code can be executed after callback update. If this is the case, you will need to find out the code and modify/correct it.

In any case, the CallbackPanel does not modify scroll position directly. It neither maintains it nor updates it.

Thanks!
bobwolf
Posted: Monday, March 9, 2009 9:12:57 AM
Rank: Member
Groups: Member

Joined: 5/31/2008
Posts: 25
Yes! You are correct!

Was my fault. I calling callbackpanel Update method via javascript, and the anchor # was causing the scroll problems. I do a few changes, putting 2 panels, and seems that i'm in the correct path.
=)

tks for quick reply!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.