ASP.NET 2.0 Maintain Scroll Position on PostBack with Mozilla FIREFOX in the works?

[ed]

Does anyone know if ASP.NET 2.0 is going to incorporate "maintain scroll
position on postback" in non-IE browsers like Firefox?

This seems like an often requested feature on these newsgroups since the
beta version of .NET.

Microsoft heavily advertises it's .NET browser detection advantages, why not
make some use of it and hope that Microsoft follows up their words with
actions? as well as following up on their agreement from the anti-trust
settlements on being anti-competitive.

Thanks.

 

[Nicholas Paldino [.NET/C# MVP]]

I would think that this is a browser issue, and not a back end issue...
After all, it's the browser that has to remember what the position is.

Now if those browsers support maintaining that position, by requiring a
certain tag, or something in the markup, then by all means, ASP.NET should
support it. If it doesn't, however, the architecture is not so closed that
you can't do it yourself.

 

[ed]

Typical MVP answer!

This is where Microsoft should step in and do it. It would be so much easier
on us all that Microsoft get this done as opposed to having customize and
build up a feature whereas Microsoft only has to tweak their version to work
in other non-IE browsers such as Firefox and Safari.

If Microsoft wants to REDUCE the amount of code, this would be a good place
to start.

I would think that this is a browser issue, and not a back end issue...
After all, it's the browser that has to remember what the position is.

Now if those browsers support maintaining that position, by requiring a
certain tag, or something in the markup, then by all means, ASP.NET should
support it. If it doesn't, however, the architecture is not so closed that
you can't do it yourself.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Does anyone know if ASP.NET 2.0 is going to incorporate "maintain scroll
position on postback" in non-IE browsers like Firefox?

This seems like an often requested feature on these newsgroups since the
beta version of .NET.

Microsoft heavily advertises it's .NET browser detection advantages, why
not
make some use of it and hope that Microsoft follows up their words with
actions? as well as following up on their agreement from the anti-trust
settlements on being anti-competitive.

Thanks.

 

[Lucas Tam]

Typical MVP answer!

Why does Microsoft have the MVP program anyways?

 

[Willy Denoyette [MVP]]

Typical MVP answer!

This is where Microsoft should step in and do it. It would be so much
easier
on us all that Microsoft get this done as opposed to having customize and
build up a feature whereas Microsoft only has to tweak their version to
work
in other non-IE browsers such as Firefox and Safari.

If Microsoft wants to REDUCE the amount of code, this would be a good
place
to start.

Ever heard that this is still in beta?
Good reason to post to the appropriate Whidbey
NG -microsoft.private.whidbey.aspnet.pageframework - instead of multiposting
to non related NG's.

Willy.

 

[Ben Amada]

Ed,

The article below addresses maintaining scroll position on postback with IE,
Firefox and other browsers:

Maintaining Scroll Position on Postback
http://aspnet.4guysfromrolla.com/articles/111704-1.aspx

Ben

 

[Guest]

Tanks Ben, it works!!!!

Ed,

The article below addresses maintaining scroll position on postback with IE,
Firefox and other browsers:

Maintaining Scroll Position on Postback
http://aspnet.4guysfromrolla.com/articles/111704-1.aspx

Ben

 

[James Curran]

I would think that this is a browser issue, and not a back end issue...
After all, it's the browser that has to remember what the position is.

Um... No.. You & I may realize that on a post back, the browser is
redisplaying the same page, but as far as the browser is concerned, it's a
different page.

--
Truth,
James Curran
[erstwhile VC++ MVP]
Home: www.noveltheory.com Work: www.njtheater.com
Blog: www.honestillusion.com Day Job: www.partsearch.com

 

[Ken Cox [Microsoft MVP]]

Don't forget to make your views known where something can be done about
it....

MSDN Product Feedback Center

http://lab.msdn.microsoft.com/productfeedback/default.aspx