[Bug 10997] add clear indication of whether an element is singleton or open/close

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10997

--- Comment #6 from Jim Michaels <jmichae3@yahoo.com> 2010-10-10 05:32:41 UTC ---
sorry.  I am a little slow on the uptake.  I have been processing these by
looking at emails rather than looking at the bug report itself, which is a
mistake.  I don't usually do this.

would you consider moving this information from the syntax section to the
description of the individual style elements themselves?

at least put in a one-liner blurb near the top saying something like 

"Singleton tags are called void elements in the <a href="link">syntax area</a>
of this document. Open/close tags are tags that are not listed onder the list
of void elements. singleton tags in xhtml and html5 must be closed with a / as
in <input ... /> or <br /> rather than the old method of <br>." 

I don't know if the latter part of this statement is true for html5, but
w3schools is putting forth that to future-proof your html you must close all
your tags.  If this is true, you may as well mention how to do this in the spec
right now, or at least tell them that in html5 it is optional.

please place this or a statement similar to it near the top of the document. 
please do this for the html5 document and the html 4 document and xhtml
documents as well if possible.  it would clear so much up.  even just this one
line.  

The word "Syntax" doesn't hold much meaning for most authors.  I didn't even
know there was a syntax section of the document.  
To be honest, the main place I as an author look is at the top of the document
to see if there are any explanations written there that I need to heed, and the
sections that deal with the tags themselves, and the attributes.  I may
occasionally venture outside of that.

I don't know if you had considered that your target audience might consist of
web authors and developers, but it does.  please consider them a little (one
line of text can make a huge difference in clearing up confusion). 


OK I understand I have been coding my optgroup elements incorrectly now,
because its content is other elements (oops).  the validator didn't like my
open/close optgroup tags with text in them (but then maybe that was the
problem).

ok, I'm not perfect at finding things.  I will let you know if my improved code
doesn't work well on the validator. if it works correctly I'll shut up about
it.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 10 October 2010 05:32:44 UTC