DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Wed, 15 Aug 2007 10:19:57 +0200,    posted on: microsoft.public.dotnet.framework.aspnet        back       

Thread Index
  1    Axel Dahmen am


HELP: Page.MaintainScrollPositionOnPostback implementation   
Hi,

I've tried using the Page.MaintainScrollPositionOnPostback property to keep
the users' focus on the web control they are currently editing on
AutoPostBack=true. Yet, there are cases when I DON'T want the scroll
position to be maintained on postback, e.g. when server-side errors occur,
being displayed at the top of the page.

With MaintainScrollPositionOnPostback=true users don't get to see the error
list and, thus, wonder why they can't submit the page.

I've tried to set the MaintainScrollPositionOnPostback property
conditionally, but I noticed an awkward behaviour of the
MaintainScrollPositionOnPostback: It is NOT being interpreted for the
current render cycle, but instead it only defines how the page behaves with
the NEXT postback.

This brings up two questions:

a) Why is this property defined as a property instead of being a Page
directive if it can be set to a constant value only?

b) Is there a workaround? MaintainScrollPositionOnPostback seems to render
client code which is interpreted and used for the next render cycle if
present. Is it possible to conditionally suppress the
MaintainScrollPositionOnPostback information returned by the "first"
postback?

TIA,
Axel Dahmen
Date:Wed, 15 Aug 2007 10:19:57 +0200   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us