Viewstate question
-
I noticed that the framework wraps the viewstate hidden input element into a DIV element. Can anyone explain why it is done this way and how and if I can get rid of the div? Can I place the viewstate hidden input at the bottom of the page? Thanking you in advance.
Excellence is not an act, but a habit!
Aristotle
-
I noticed that the framework wraps the viewstate hidden input element into a DIV element. Can anyone explain why it is done this way and how and if I can get rid of the div? Can I place the viewstate hidden input at the bottom of the page? Thanking you in advance.
Excellence is not an act, but a habit!
Aristotle
No, I don't believe you can ( not easily ). Why do you want to ?
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
No, I don't believe you can ( not easily ). Why do you want to ?
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
To be honest I have to serious reason. I just like being in full control of what markup is delivered to the site visitor and little things like this one just annoy me.
Excellence is not an act, but a habit!
Aristotle
-
To be honest I have to serious reason. I just like being in full control of what markup is delivered to the site visitor and little things like this one just annoy me.
Excellence is not an act, but a habit!
Aristotle
-
I noticed that the framework wraps the viewstate hidden input element into a DIV element. Can anyone explain why it is done this way and how and if I can get rid of the div? Can I place the viewstate hidden input at the bottom of the page? Thanking you in advance.
Excellence is not an act, but a habit!
Aristotle
-
because i need the viewstate. was just wondering why it is wrapped within a DIV.
Excellence is not an act, but a habit!
Aristotle
-
Without this wrapper div ASP.NET wouldn't be able to produce valid XHTML Strict markup. As for the custom viewstate hidden input placing - I don't think it is impossible to do this, but should be complicated enough to not be worth the effort.