gt; > Message: 7
> > Date: Sun, 02 Sep 2012 15:05:58 +0200
> > From: "Charles McCathie Nevile"
> > To: whatwg
> > Subject: Re: [whatwg] "content" element, which we need in our
> > documents
> > Message-ID:
> > Content-Type: t
cCathie Nevile"
> To: whatwg
> Subject: Re: [whatwg] "content" element, which we need in our
> documents
> Message-ID:
> Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
>
> On Thu, 30 Aug 2012 20:10:15 +0200, Ian Hickson wrote:
&
On Thu, 30 Aug 2012 20:10:15 +0200, Ian Hickson wrote:
...
On Fri, 29 Jun 2012, Cameron Jones wrote:
If the content is a special section within the document you should use
the element which has semantic meaning over .
Alternatively you could use if it's distinct and
self-contained. These tw
On Fri, 29 Jun 2012, Ian Yang wrote:
>
> As many of you may have been aware that there is an important sectioning
> element we have been short of for a long time: the "content" element.
That's , as far as I can tell.
> Remember how we sectioned our documents in those old days? It's the
> meani
2012/6/29 (x-apple-data-detectors://8) Steve Faulkner mailto:faulkner.st...@gmail.com)>
>
> ARIA fills the gap in HTML with role="main"
> http://www.w3.org/TR/wai-aria/roles#main
>
> I agree that an explicit element would be nice, but the powers that be have
> rejected the idea.
>
> --
> with
Hi Steve,
Thank you. I understand.
Regards,
Ian
2012/6/29 Steve Faulkner
> Hi Ian,
>
> ARIA fills the gap in HTML with role="main"
> http://www.w3.org/TR/wai-aria/roles#main
>
> I agree that an explicit element would be nice, but the powers that be have
> rejected the idea.
>
> --
> with regar
Hi Ian,
ARIA fills the gap in HTML with role="main"
http://www.w3.org/TR/wai-aria/roles#main
I agree that an explicit element would be nice, but the powers that be have
rejected the idea.
--
with regards
Steve Faulkner
Technical Director - TPG
www.paciellogroup.com | www.HTML5accessibility.co
"sometimes looks messy"
If this is the problem, or at least one of problems, how can a wrapper of
all this mess, that is a tag, could solve the problem ?
It will just add another node in DOM tree in this case without a real
benefit.
On Fri, Jun 29, 2012 at 4:03 PM, Ian Yang wrote:
> By analyzi
more organized for who? the author or the consumer?
this is author aesthetics.
On Fri, Jun 29, 2012 at 3:03 PM, Ian Yang wrote:
> By analyzing the example in HTML5 spec, wrapping all content elements can
> make the structure of the document become more organized. After all,
> content elements al
By analyzing the example in HTML5 spec, wrapping all content elements can
make the structure of the document become more organized. After all,
content elements all being at the same level of and is
unreasonable, and sometimes looks messy, especially when there are many
different kinds of content
So, how do you propose to define what represents?
As a container element it is a thematic grouping. This is identical to
which is a thematic grouping with hierarchical context.
What do you want to be able to do? If it is to simply lookup the
"content" of the page as a unique concept, this is de
I agree with Ian about the use of and , the
specifications are really clear on those elements. The are used to wrap an
entire entry, not the "content" (in the meaning Ian stated).
The read question for me is: What is the problem of having the content at
the same level of and (for example inside
As described in whatwg specs, a , in this context, is a thematic
grouping of content, typically with a heading.
As for a , which usually contains its own and ,
is used to form an independent content like blog entry, comment, or
application.
Both section and article elements are not the candidate
If the content is a special section within the document you should use
the element which has semantic meaning over .
Alternatively you could use if it's distinct and
self-contained. These two elements serve to disambiguate the abstract
idea of content into something with semantic meaning which ca
Please note that the example of the nav in HTML5 spec uses to wrap
all the contents of the page other than the header and footer.
And developers always wrap contents with or . Your website does that, too.
If everything is content, then we would have never seen codes mentioned
above.
Regards,
Ian Yang wrote:
>Hi editors in chief and everyone else,
>
>How have you been recently?
>
>As many of you may have been aware that there is an important
>sectioning
>element we have been short of for a long time: the "content" element.
>
>Remember how we sectioned our documents in those old days
Hi editors in chief and everyone else,
How have you been recently?
As many of you may have been aware that there is an important sectioning
element we have been short of for a long time: the "content" element.
Remember how we sectioned our documents in those old days? It's the
meaningless s. We
17 matches
Mail list logo
