RE: maincontent element - HTML5 extension specification (further updates and correct URL)

Steve,

Thank you for the clarification, that makes sense to me.

Jon


From: Steve Faulkner [mailto:faulkner.steve@gmail.com]
Sent: Friday, October 12, 2012 12:16 PM
To: Gunderson, Jon R
Cc: HTMLWG WG
Subject: Re: maincontent element - HTML5 extension specification (further updates and correct URL)

Hi Jon,

the spec[1] restricts ancestors not children:

"Where Flow content is expected, but with no article, aside, footer, header or nav element ancestors."

so <maincontent> can contain any of the above elements, but cannot be contained within those elements.




[1] https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html


regards
SteveF

On 12 October 2012 17:59, Gunderson, Jon R <jongund@illinois.edu<mailto:jongund@illinois.edu>> wrote:
Steve,

Thank you for developing this HTML5 extension for main content.

Is this specification also dependent on changing the types of content that can be in a article.

I noticed that the extension says that an ARTICLE element cannot be a child of MAINCONTENT element.

That may be quite restrictive to authors who may be using the ARTICLE element as a way to separate stories or if the main content is a blog.

I can see restricting other elements like ASIDE, FOOTER, HEADER or NAV elements.

What was the purpose of trying to exclude ARTICLE element as a child?

Jon



From: Steve Faulkner [mailto:faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>]
Sent: Friday, October 12, 2012 10:48 AM
To: HTMLWG WG
Subject: Re: maincontent element - HTML5 extension specification (further updates and correct URL)

further updated after  feedback from Simon Pieters (thanks)
and also got the correct URL (one that points to latest version) from annevk.(thanks)

https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html

feedback welcome!


regards
SteveF
On 12 October 2012 15:23, Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>> wrote:
FYI

I have updated the spec after feedback from Marcos Caceres (with thanks)  and transferred it to the w3c server
https://dvcs.w3.org/hg/html-extensions/raw-file/3acee7f50663/maincontent/index.html


feedback welcome

--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com<http://www.paciellogroup.com> | www.HTML5accessibility.com<http://www.HTML5accessibility.com> | www.twitter.com/stevefaulkner<http://www.twitter.com/stevefaulkner>
HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/<http://dev.w3.org/html5/alt-techniques/>
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
<http://www.paciellogroup.com/resources/wat-ie-about.html>



--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com<http://www.paciellogroup.com> | www.HTML5accessibility.com<http://www.HTML5accessibility.com> | www.twitter.com/stevefaulkner<http://www.twitter.com/stevefaulkner>
HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/<http://dev.w3.org/html5/alt-techniques/>
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
<http://www.paciellogroup.com/resources/wat-ie-about.html>



--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com<http://www.paciellogroup.com> | www.HTML5accessibility.com<http://www.HTML5accessibility.com> | www.twitter.com/stevefaulkner<http://www.twitter.com/stevefaulkner>
HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/<http://dev.w3.org/html5/alt-techniques/>
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
<http://www.paciellogroup.com/resources/wat-ie-about.html>