Figured as much. This particular app. is for external users, but is a
management app. (not many users), not the main customer-facing application.
Basically there was an edict of "client code only when necessary" -- and
also laziness on my part. But basically, you're right.
So, any pointers to the preferred way to do this? (Figured there'd be a
declaritive way to do this and have the framework handle it, even if it
generated client scripting - but maybe not.)
thanks
"Raterus" <mo*********@suretar.reverse> wrote in message
news:ue**************@TK2MSFTNGP09.phx.gbl...
Not to question you as I'm sure you have a good reason, but why are you
trying to avoid client-side code in this situation? Doesn't this problem
beg for it?
To answer your question, no, you can't maintain scroll/focus w/o writing
client-side code. Sure you can write code to do it on the server, but it is
still going to be clientside code. I'd try to avoid the postback as much as
possible, unless this is an intranet app and nobody will ever notice.
--Michael
"Mike" <vi********@yahoo.com> wrote in message
news:e$****************@TK2MSFTNGP10.phx.gbl...
I have a few textbox controls that have autopostback so that when they
loose focus they update a label control that shows the count of characters in
their respective text control. This works fine, except that after the
postback, the page is shown reset -- scrolled to the top and with no
control having focus. Can I maintain scroll/focus w/o writing client-side
scripting?
thanks