ASP.Net 2.0 and the annoying <div> wrappers

[Guest]

Hi you all,

I've just downloaded the latest beta of the .Net Framework and Visual Studio
Expression 2005 edition. I only created a simple ASPX file with some
code-beside/behind (however you want to call it). First thing I checked was
the generated html-output and I was shocked! I found <div>-tags everywhere
.... what are they for? which w3c standard or recommendation was intended to
be covered by this tags???

However I thought I could get rid of them by creating my own HtmlTextWriter,
BUT this didn't work. In case you inherit from Html32TextWriter the page will
always use that <div> tags. Does anyone have an idea?

How can I get rid of those <div>-Tags???

Thanks in advance.
Patrick

 

[Patrice]

What controls do you have on your page ? What browser are you using ?

Still using Visual Web Devleoper beta 1 here...

Patrice

 

[Guest]

Hi Patrice,

no matter what control the viewstate hidden-fields are already wrapped
around such a <div>-tag. I'm using Internet Explorer 6.x.

Patrick

 

[TDAVISJR]

Obviously you have something against the <div> tag. They will do no harm to
the way your page renders. However, to turn them off try switching the
browser validation at the top. Currently it might be set to XHTML (which
use <div> tags alot), you can try changing it to IE 6 or even lower.

 

[Guest]

Hi TDAVISJR,

Are you sure this validation works? I will give it a try.
However, I would still like to know what this <div> tags are for? Why should
the page ouput size be increased by any tags which are not used or even have
no effect? WHAT FOR???

Thanks
Patrick

 

[TDAVISJR]

At your request:

http://webdesign.about.com/cs/htmltags/a/aa011000a.htm
http://webmonkey.wired.com/webmonkey/html/97/19/index2a.html

The point is, if you are going to be using CSS for layout alot, then <div
tags are the way to go. If you still use the old layout HACK by using html
tables, then there is no need for <div>

 

[Guest]

Hi TDAVISJR,

I understand and know the benifits of a <div> tag, but why should someone
surround "<input type='hiddne' ... />" fields with a <div> tag. I do not
understand that... Sorry. Could you (or anybody else) enlight me?

Thanks
Patrick

 

[Kevin Spencer]

Hi Patrick,

As you've observed, there is no reason to have a div tag around a hidden
form field. On the other hand, there is no harm in having a div tag around a
hidden form field. The div tag is part of the base class, and it's simpler
and more efficient to just leave it in than to create some workaround to
remove it, or create some other base class to add to the model.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.

 

[Patrice]

Ok same here with the previous release. All "standard" (EVENTXXX And
VIEWSTATE) hidden fields are embedded in to a single div section... User
hidden fields are not embedded into a DIV tag.

IMO your best bet would be to suggest removing this tag in case it was not
made on purpose. Anyway it doesn't seem to cause any problem here....

Patrice

--