The W3C Validator tells me I can't put block-level elements inside inline elements. Makes sense...
but what if I'm using CSS to change that block-level element into an inline element?
And what if I'm using CSS to convert an inline element into a block-level element (when inside another inline element)?
The Validator doesn't pick up on this obviously, but is it wrong?
(I'm not actually doing this, I'm just wondering about best-practice)
Note: An inline element cannot contain a block-level element!
Generally, block-level elements may contain inline elements and (sometimes) other block-level elements. Inherent in this structural distinction is the idea that block elements create "larger" structures than inline elements.
Yes, you can have nested block elements. You may need to use floats or positioning to keep them from stacking though. I think you may be confusing having a block element child of a block element (good) with a block element that is a child of an inline element (will probably render fine; but violates standards).
By default, inline elements do not force a new line to begin in the document flow. Block elements, on the other hand, typically cause a line break to occur (although, as usual, this can be changed using CSS).
An element defined as a block element in the HTML specification is not the same as a element defined as display: block;
in CSS.
With this I mean: Even if you say <p style="display: inline;">Lorem...</p>
. The <p>
will still be a block element in the eyes of HTML.
HTML, CSS and JavaScript if used right is said to have loose coupling toward each other and that one should not be dependent of another and that the absence of one should not make the others (or the system as whole) fail.
An element that is inline elements should not contain block elements. Block elements can contain block and/or inline elements while inline elements can only contain other inline (including inline-block
, such as <img>
) elements.
You can of course do it anyways, since the graphical representation will be pretty consistent across browsers. It's still not something I'd recommend though, and can't really think of a reason to do it either.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With