Hi Dusan, Here are some of the unofficial guidelines I work with:
<div /> will not work with IE in certain circumstances. It might give you some errors which you might find mind-bogglingly difficult to debug (i.e. very weird behaviour). <div></div> will behave much better, but (unless you have an ID or a class on it) I suggest you do not use empty <div>s at all. I certainly don't use them. What's the real need for it if you think about it really? As far as <input /> is concerned, it is a sort of a special tag in so far that all its attributes are defined within the tag (i.e. value, type, name, id, class, size, maxlength, etc.), so there is no need for any content between the opening and closing tags, hence in XHTML we use <input type="" value="" name="" />. This is valid XML and it conforms to the standards. Hope this helps. Regards, Jason www.flexewebs.com On 11/25/07, Dusan Smolnikar <[EMAIL PROTECTED]> wrote: > > I'm afraid browser don't agree with this, though. I'm not sure about > input but I'm > positive that <div></div> is not the same as <div /> as far as browser > rendering > goes. > > > On Nov21, 2007, at 7:28 AM, Kepler Gelotte wrote: > > > Actually as far as XML (and consequently XHTML) is concerned: > > > > <input type="text" name="a" value="a"></input> > > > > Is the same as: > > > > <input type="text" name="a" value="a" /> > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
