The current spec, which was updated in response to some previous issues, reads:

   # A run-in element (or pseudo-element) A behaves as follows:
   #
   #   1. If A has any children that inhibit run-in behavior (see below),
   #      then A is rendered as if it had 'display: block'.
   #   2. Let B be the first of A's following siblings that is neither
   #      floating nor absolutely positioned nor has 'display: none'.
   #      If B exists and has a specified value for 'display' of 'block'
   #      or 'list-item' and is not replaced, then A is rendered as an
   #      'inline' element at the start of B's principal box. Note: A
   #      is rendered before B's ':before' pseudo-element, if any.
   #      See 12.1.
   #   3. Otherwise, A is rendered as if it had 'display: block'.
   #
   # In the above, "siblings" and "children" include both normal elements
   # and :before/:after pseudo-elements.
   #
   # An element or pseudo-element C inhibits run-in behavior if one of
   #  the following is true. (Note 

Similar:

1. [CSS21] list-item box generation – editorial issues Issue 1. 9.2.1 (Block-level elements and block boxes) says:[1] # Some block-level elements generate additional boxes outside of the # principal box: 'list-item' elements. These...
2. [CSS21] Titles in Chapter 10 – trivial editorial issues The following are titles in Chapter 10: 10.3.9 'Inline-block', non-replaced elements in normal flow 10.3.10 'Inline-block', replaced elements in normal flow 10.6.2 Inline replaced elements,...
3. [CSS21] Issue 121 (was: Issues with inline formatting model (particularly 10.8)) This is text to resolve issue 121[1], which refers to item 9 in Anton Prowse's e-mail[2]. Modify these two paragraphs in 10.8.1[3] as follows (indicated...
4. [CSS21] The width/height properties list-item, run-in and table-* display types The 'width' property (10.2) applies to all elements except non-replaced inline elements, table rows and row groups. However, (1a) nothing in the spec seems to...
5. [CSS21] pseudo-elements and generated content – editorial issues There appear to be some areas of the spec in which the use of the term "elements" should include pseudo-elements and generated content. Issue 1....

This entry was posted on Wednesday, September 22nd, 2010 at 6:37 am and is filed under dotnet, vb, vb.net. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.