WHAT a li

Line 1191, Column 15: The first occurrence of ID searchbox was here. id="searchbox">

Line 1189, Column 21: Bad value for attribute id on element input:

An ID must not contain whitespace.  

style="display:none" 

Syntax of id:An ID consists of at least one character but must not contain any whitespace.

<input type="submit"

value="Search"

class="submit"

style="display:none">

 

 

Line 1378, Column 18: Bad value {Year}-{MonthNumberWithZero}-{DayOfMonthWithZero} for attribute datetime on element time: The literal did not satisfy the date or time format. pubdate="pubdate">Posted {TimeAgo}</time>

Syntax of date or time:(This format deviates from the spec draft.) An ISO 8601 date (i.e. YYYY-MM-DD.), time (i.e. hh:mm optionally followed by :ss optionally followed by . and digits) optionally with a time zone designator (i.e. either Z, +hh:mm or -hh:mm) or both date and time separated by T. Examples: 1996-01-01T12:05:25, 1996-01-01, 12:05:25, 1996-01-01T12:05:25.6-02:00

Line 1576, Column 6: Stray end tag div. </div><!-- /.container -->

3.3.3.1. Block-level elements

Block-level elements are used for structural grouping of page content.

There are several kinds of block-level elements:

• Some can only contain other block-level elements: blockquote, section, article, header.
• Some can only contain inline-level content: p, h1-h6, address.
• Some can contain either block-level elements or inline-level content (but not both): nav, aside, footer, div.
• Finally, some have very specific content models: ul, ol, dl, table, script.

There are also elements that seem to be block-level but aren't, such as body, li, dt, dd, and td. These elements are allowed only in specific places, not simply anywhere that block-level elements are allowed.

Some block-level elements play multiple roles. For instance, the script elements is allowed inside head elements and can also be used as inline-level content. Similarly, the ul, ol, dl, table, and blockquote elements play dual roles as both block-level and inline-level elements.

3.3.3.2. Inline-level content

Inline-level content consists of text and various elements to annotate the text, as well as some embedded content (such as images or sound clips).

Inline-level content comes in various types:

Strictly inline-level content Text, embedded content, and elements that annotate the text without introducing structural grouping. For example: a, meter, img. Elements used in contexts allowing only strictly inline-level content must not have any descendants that are anything other than strictly inline-level content. Structured inline-level elements Block-level elements that can also be used as inline-level content. For example: ol, blockquote, table.

Some elements are defined to have as a content model significant inline content. This means that at least one descendant of the element must be significant text or embedded content.

Unless an element's content model explicitly states that it must contain significant inline content, simply having no text nodes and no elements satisfies an element whose content model is some kind of inline content.

Significant text, for the purposes of determining the presence of significant inline content, consists of any character other than those falling in the Unicode categories Zs, Zl, Zp, Cc, and Cf. [UNICODE]

The following three paragraphs are non-conforming because their content model is not satisfied (they all count as empty).

<p></p> <p><em>&#x00A0;</em></p> <p> <ol> <li></li> </ol> </p>

Embedded content consists of elements that introduce content from other resources into the document, for example img. Embedded content elements can have fallback content: content that is to be used when the external resource cannot be used (e.g. because it is of an unsupported format). The element definitions state what the fallback is, if any.

3.3.3.3. Transparent content models

Some elements are described as transparent; they have "transparent" as their content model. Some elements are described as semi-transparent; this means that part of their content model is "transparent" but that is not the only part of the content model that must be satisfied.

When a content model includes a part that is "transparent", those parts must only contain content that would still be conformant if all transparent and semi-transparent elements in the tree were replaced, in their parent element, by the children in the "transparent" part of their content model, retaining order.

When a transparent or semi-transparent element has no parent, then the part of its content model that is "transparent" must instead be treated as zero or more block-level elements, or inline-level content (but not both).

3.3.3.4. Determining if a particular element contains block-level elements or inline-level content

Some elements are defined to have content models that allow either block-level elements or inline-level content, but not both. For example, the aside and li elements.

To establish whether such an element is being used as a block-level container or as an inline-level container, for example in order to determine if a document conforms to these requirements, user agents must look at the element's child nodes. If any of the child nodes are not allowed in block-level contexts, then the element is being used for inline-level content. If all the child nodes are allowed in a block-level context, then the element is being used for block-level elements.

Whenever this search would examine a transparent element, the element's own child nodes must be examined instead, potentially recursing further if any of those are themselves transparent.

For instance, in the following (non-conforming) XML fragment, the li element is being used as an inline-level element container, because the meta element is not allowed in a block-level context. (It doesn't matter, for the purposes of determining whether it is an inline-level or block-level context, that the meta element is not allowed in inline-level contexts either.)

<ol> <li> <p> Hello World </p> <meta title="this is an invalid example"/> </li> </ol>

In the following fragment, the aside element is being used as a block-level container, because even though all the elements it contains could be considered inline-level elements, there are no nodes that can only be considered inline-level.

<aside> <ol> <li> ... </li> </ol> <ul> <li> ... </li> </ul> </aside>

On the other hand, in the following similar fragment, the aside element is an inline-level container, because the text ("Foo") can only be considered inline-level.

<aside> <ol> <li> ... </li> </ol> Foo </aside>

3.11.2. The ul element

Block-level element, and structured inline-level element.

Contexts in which this element may be used: Where block-level elements are expected. Where structured inline-level elements are allowed. Content model: Zero or more li elements. Element-specific attributes: None. DOM interface: No difference from HTMLElement.

The ul element represents an unordered list of items (which are represented by li elements).

The items of the list are the li element child nodes of the ul element.

3.11.3. The li element

Contexts in which this element may be used: Inside ol elements. Inside ul elements. Inside menu elements. Content model: When the element is a child of an ol or ul element and the grandchild of an element that is being used as an inline-level content container, or, when the element is a child of a menu element: inline-level content. Otherwise: zero or more block-level elements, or inline-level content (but not both). Element-specific attributes: If the element is a child of an ol element: value If the element is not the child of an ol element: None. DOM interface: interface HTMLLIElement : HTMLElement { attribute long value; };

The li element represents a list item. If its parent element is an ol, ul, or menu element, then the element is an item of the parent element's list, as defined for those elements. Otherwise, the list item has no defined list-related relationship to any other li element.

When the list item is the child of an ol or ul element, the content model of the item depends on the way that parent element was used. If it was used as structured inline content (i.e. if that element's parent was used as an inline-level content container), then the li element must only contain inline-level content. Otherwise, the element may be used either for inline content or block-level elements.

When the list item is the child of a menu element, the li element must contain only inline-level content.

When the list item is not the child of an ol, ul, or menu element, e.g. because it is an orphaned node not in the document, it may contain either for inline content or block-level elements.

When used as an inline-level content container, the list item represents a single paragraph.

The value attribute, if present, must be a valid integer giving the ordinal value of the first list item.

If the value attribute is present, user agents must parse it as an integer, in order to determine the attribute's value. If the attribute's value cannot be converted to a number, it must be treated as if the attribute was absent. The attribute has no default value.

The value attribute is processed relative to the element's parent ol element (q.v.), if there is one. If there is not, the attribute has no effect.

The value DOM attribute must reflect the value of the value content attribute.

Unordered List: UL, LI

The UL represents a list of items -- typically rendered as a bulleted list.

The content of a UL element is a sequence of LI elements. For example:

<UL> <LI>First list item <LI>Second list item <p>second paragraph of second item <LI>Third list item </UL>

{block:Contributors}

<div class="column" style="padding-right:0;">

starts section id contributors<section id="contributors">

<h1>Contributors</h1>heading for contributors

<ul>

{block:Contributor collapsible="true" count="10" action_id="see_more_contributors"}

{block:ContributorMore}

this li has no class
<li><a href="#" id="see_more_contributors">View all {NumContributors}
contributors &raquo;</a></li>

{/block:ContributorMore}

this li has no class
<li><a href="{ContributorProfileLink}" rel="contributor"
title="{ContributorName}'s profile"><img src="{ContributorPortraitURL-20}" alt="{ContributorName}"></a>
<a href="{ContributorProfileLink}" rel="contributor">{ContributorName}</a></li>

{/block:Contributor}

</ul>

ends section id contributors </section>

 

</div>

{/block:Contributors}

to compare to the error below

{block:HasPages}

<nav id="navigation">

<ul>

{block:Pages}

it is inside the sub-block PAGES which is a child of MR. BLOCK HASPAGES
it is wrapped by its parent GRANDPARENT MR. BLOCK HASPAGES'
'nav id "navigation"
 AND
serves as list element for it's parent MR. BLOCK PAGES
IT ITSELF CONTAINS
a URL
class
this li has
rel
bracketed 'label' link
IT IS ONLY THE LIST ELEMENT FOR THE UL INSIDE ITS PARENTS MR. AND MRS. BLOCK PAGES
WHICH IS ONLY WRAPPED BY ITS GRANDPARENT MR. HASPAGES NAV divisioney thing
it's the sublist of its grandparents and
the list of its parents mr. and mrs. pages
<li><a href="{URL}" class="{Current}" rel="{External}">{Label}</a></li>

{/block:Pages}

</ul>

</nav>

{/block:HasPages}

Weirdopedia says: "Weird" http://weirdopedia.posterous.com/what-a-li Line 1191 , Column 15 : The first occurrence of ID searchbox was here. id="searchbox" > Line 1189 , Column 21 : Bad value for attribute id on element input: An ID must not contain whitespace.   style="display:none"   Syntax of id:An ID consists of at least one character but must not contain any whit ...