W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] wrapper element

From: usuario <soyhobo@gmail.com>
Date: Mon, 28 Feb 2011 18:46:10 +0000
Message-ID: <AANLkTik3pV1sEN9ZNEDswiNz6Xec=HVwxtSkE31tqU_3@mail.gmail.com>
[Had problems sending my mails to the list, resending message]

Some of you may be questioning why a wrapper element if it has not
semantics, the thing is, It DO have semantics.

Wrapper:
a container element whose solely purpose is to isolate flow content for
visually appealing purposes. It it usually used for applying margin, padding
to inner elements, and dimensionally separating them from its real parent.

*example, consider:*

<header>
    <div class="wrapper">
        <h1>Header 1</h1>
        <p>this content is centered because margin: 0 auto is applied to
parent of div.wraper element</p>
        I have always worked, I'm almost standard, sometimes people don't
call me wraper but 'container' or 'content' instead
    </div>
</header>

*Against:*

<header>
    <wrapper>
        <h1>Header 1</h1>
        <p>this content is centered because margin: 0 auto is applied to
parent of wrapper element</p>
        I think I'm more semantic because I'm specifically designed for this
task, and I do it very well. What do you think?
    </wrapper>
</header>

Moreover.

> Why not borrow the <g> from SVG (meaning "to group together" -- the
> semantics may be a bit more accessible in some cross-linguistic sense than
> <wrap>, particularly because of the silent "w" in "wrap" which throws a lot
> of folks for a loop)?
>

Don't know if that's the solution, i just don't discard it.


> <div> carries no semantic meaning. * If you are using it for such, the
> semantic is purely internal to your application*, and thus doesn't
> carry the common meaning of "semantics" as used on the web.
>

We have no problems with <div> definition. But i think you are not right in
your statement.
Answer this, Are wrappers purely internal to my(of mine) application? that's
a capitalized lie, just think on it. Most applications use a wrapper-like
div. You had, and i don't know you.

We have to start deciding what do we want from html5, at what degree do we
want a more semantic web? why just <header>, why just <footer>.

I can assure you the world was fine with <div id="header">, but so, why
<header> was created for? It was created because being so widely used,
somebody believed it was *more semantic* to convert it into an element.

<div> is the wrapper element.  That's its entire purpose for living.  ^_^
>

<div> was not creating for wrapping things, but for contain them. When you
wrap something, you are giving it a different implicit meaning to that
wrapper div.
Received on Monday, 28 February 2011 10:46:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC