Is this bad practice XHTML? (block element coming directly after inline element)

[aqw]

Hi!

Is this bad practice XHTML?

<a href="google.co.uk">Aha!</a>

<ol>
<li>...</li>
...
</ol>

I mean a block-level element coming directly after an inline element. It is valid for the w3 validator in chtml strict mode (I don't trust it a yota though). Thanks!

[Dan Schulz]

It's valid, but not how I would do things.

I'd have the anchor inside a block level element, and then have the list come after that (the block level element, not the anchor).

For example:

<div>
    <a href="#">Some Link</a>
</div>
<ol>
    <li>List Item</li>
    <li>List Item</li>
</ol>

[Stormrider]

What's wrong with a block element coming after an inline one?

[AutisticCuckoo]

It's a logical oddity. An element should normally contain either block-level elements or inline elements, not both. The HTML spec allows the mix, but it doesn't really make sense (not to me, at least).

When content like this is rendered by a CSS-compliant user agent, the inline elements will be surrounded by what is called 'anonymous block boxes', because it doesn't make sense to mix block-level and inline content at the same structural level.