Re: [whatwg] Is main now an official HTML5 element?
Ian Yang, 2013-02-14 03:21 (Europe/Helsinki): !DOCTYPE html titlelorem ipsum/title header ... /header main id=main role=main ... /main footer ... /footer I find the logic to be that if you use header and/or footer you should wrap the main content within main. Then use section and article for the structure. One thing worth noting is that unlike id=main or role=main, the main is intended to be used (nested) multiple times on a page. So, following markup does make sense: !DOCTYPE html html ... body header.../header main ul liarticle header.../header main.../main footer.../footer /article/li liarticle header.../header main.../main footer.../footer /article/li /ul /main footer.../footer /body /html The first header (body header) hopefully contains the page main header (perhaps blog title and slogan, maybe site navigation in nav) and within the first main (body main) is a list of articles (perhaps blog entries?) where each article has its own header (article header), main part (article main) and the footer (article footer). (Note that the selectors that I used within the parentheses are generic and should work equally well on any page that uses main element.) In the real world, the main part pretty much always requires some container (usually for styling and scripting) anyway so better standardize main for that, IMHO. I know Ian does/did not agree because in theory that is not needed because the main part is everything minus header minus footer. However, it turns out that neither CSS or JS can handle that really well. In the end, the WHATWG was supposed to be about real world usage vs. theoretical correctness and this is one example of that. If the content is authored this way, UA could provide a navigation aid called skip to the start of the next piece of content instead of the current global skip to the content implementation allowed by id=main or role=main which would be usually the same as end of htmlbodyheader. -- Mikko
Re: [whatwg] Is main now an official HTML5 element?
Chaals wrote: The HTML WG is one of the working groups of W3C. The working group has a charter that describes some of how it works: http://www.w3.org/2007/03/HTML-WG-charter for those interested there is the up to date proposed charter which is being reviewed currently: http://www.w3.org/html/wg/charter/2012/ regards SteveF
Re: [whatwg] Is main now an official HTML5 element?
On Thu, 14 Feb 2013, Steve Faulkner wrote: Partially agree, it matters what conformance checkers implement and in the case of main. the major HTML conformance checker will implement the conformance rules in the W3C HTML spec. This will leave the WHATWG spec not matching reality. When it comes to conformance requirements, the reality that is most important to follow is usage, not validator implementations. But input from validator implementors is naturally taken into consideration. Should there be specific feedback from Henri or Mike on this topic, I will naturally examine it along with all other feedback. It should also be noted that as implemented in browsers main is implemented as per the W3C spec i.e. main is mapped to role=main and because of this main is interpreted by AT as a main landmark already. This leaves the WHATWG spec not matching reality. The spec already matches reality here as far as I can tell. Beyond the priorities and domain of the browser vendors is the conformance requirements and advice the HTML spec provides to authors which can directly impact the experience for users. So I suggest non browser differences matter very much. Agreed. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Is main now an official HTML5 element?
On Wed, 13 Feb 2013, Ian Yang wrote: I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? main is currently in the HTML standard. That doesn't mean much, though. What means something is that main is now implemented by two browsers in their development builds. Once they ship in final versions, that's the point at which we know that the feature is part of the platform. However, in spec, it still says that main element is not a sectioning element. Correct. Broadly speaking, sectioning elements are those with headings; main doesn't typically have a heading, it contains the content after the heading, distinguishing it from the content that is merely heading and navigation and so forth. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. I'm not sure what you mean here. The main content doesn't appear in the outline; the outline only contains the headers, essentially. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? There's already corresponding sectioning elements to indicate something that is main content -- article or section, depending on what exactly the content is. The spec goes into some detail about this, including with examples, here: http://whatwg.org/html#the-main-part-of-the-content http://whatwg.org/html#the-main-element http://whatwg.org/html#usage-summary-0 http://whatwg.org/html#sample-outlines -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Is main now an official HTML5 element?
Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner faulkner.st...@gmail.comwrote: Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an open bug on that, which we be dealt with. If you want to discuss the specification of the main element in HTML 5.1 specification feel free mail the html wg list. If you want to discuss definition as per the whatwg spec this is the place, although I will obviously follow ant discussions with interest regards SteveF Date: Wed, 13 Feb 2013 18:31:32 +0800 From: Ian Yang i...@invigoreight.com To: whatwg wha...@whatwg.org Subject: [whatwg] Is main now an official HTML5 element? Message-ID: CABr1FsfcaX8=B8TReG8Sz36W= h1w0hRY61+LG=cebo-zuwy...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi editors and all other folks, I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? However, in spec, it still says that main element is not a sectioning element. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? Sincerely, Ian Yan
Re: [whatwg] Is main now an official HTML5 element?
I think this should answer your question: http://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F Best regards 2013/2/14 Ian Yang i...@invigoreight.com Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner faulkner.st...@gmail.comwrote: Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an open bug on that, which we be dealt with. If you want to discuss the specification of the main element in HTML 5.1 specification feel free mail the html wg list. If you want to discuss definition as per the whatwg spec this is the place, although I will obviously follow ant discussions with interest regards SteveF Date: Wed, 13 Feb 2013 18:31:32 +0800 From: Ian Yang i...@invigoreight.com To: whatwg wha...@whatwg.org Subject: [whatwg] Is main now an official HTML5 element? Message-ID: CABr1FsfcaX8=B8TReG8Sz36W= h1w0hRY61+LG=cebo-zuwy...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi editors and all other folks, I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? However, in spec, it still says that main element is not a sectioning element. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? Sincerely, Ian Yan -- Aurelio De Rosa email: aurelioder...@gmail.com email: a.der...@audero.it website: www.audero.it user group: ug.audero.it
Re: [whatwg] Is main now an official HTML5 element?
Hi Aurelio, I see. So whatwg mainly focus on the development of HTML and APIs needed for web applications. Thank you very much. Kind Regards, Ian On Thu, Feb 14, 2013 at 8:31 AM, Aurelio De Rosa aurelioder...@gmail.comwrote: I think this should answer your question: http://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F Best regards 2013/2/14 Ian Yang i...@invigoreight.com Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner faulkner.st...@gmail.comwrote: Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an open bug on that, which we be dealt with. If you want to discuss the specification of the main element in HTML 5.1 specification feel free mail the html wg list. If you want to discuss definition as per the whatwg spec this is the place, although I will obviously follow ant discussions with interest regards SteveF Date: Wed, 13 Feb 2013 18:31:32 +0800 From: Ian Yang i...@invigoreight.com To: whatwg wha...@whatwg.org Subject: [whatwg] Is main now an official HTML5 element? Message-ID: CABr1FsfcaX8=B8TReG8Sz36W= h1w0hRY61+LG=cebo-zuwy...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi editors and all other folks, I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? However, in spec, it still says that main element is not a sectioning element. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? Sincerely, Ian Yan -- Aurelio De Rosa email: aurelioder...@gmail.com email: a.der...@audero.it website: www.audero.it user group: ug.audero.it
Re: [whatwg] Is main now an official HTML5 element?
On Thu, Feb 14, 2013 at 1:06 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 13 Feb 2013, Ian Yang wrote: I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? main is currently in the HTML standard. That doesn't mean much, though. What means something is that main is now implemented by two browsers in their development builds. Once they ship in final versions, that's the point at which we know that the feature is part of the platform. However, in spec, it still says that main element is not a sectioning element. Correct. Broadly speaking, sectioning elements are those with headings; main doesn't typically have a heading, it contains the content after the heading, distinguishing it from the content that is merely heading and navigation and so forth. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. I'm not sure what you mean here. The main content doesn't appear in the outline; the outline only contains the headers, essentially. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? There's already corresponding sectioning elements to indicate something that is main content -- article or section, depending on what exactly the content is. The spec goes into some detail about this, including with examples, here: http://whatwg.org/html#the-main-part-of-the-content http://whatwg.org/html#the-main-element http://whatwg.org/html#usage-summary-0 http://whatwg.org/html#sample-outlines Thanks Hickson for providing information, especially those example links. In the past, I always regarded a sectioning main content area is an indispensable part in a document. Today, information above tell me that the main content area seem doesn't need to be a titled section. So it seems that the following markup contains one unnecessary section and one unnecessary h1, and they cause one unnecessary indent in document outline. !DOCTYPE html titlelorem ipsum/title header h1Branding/h1 nav h1Navigation/h1 lorem ipsum /nav /header section id=main role=main h1Main Content/h1 section h1Welcome/h1 lorem ipsum /section section h1Intro/h1 lorem ipsum /section aside id=comp role=complementary h1Complementary Content/h1 article h1Latest News/h1 lorem ipsum /article article h1Recent Comments/h1 lorem ipsum /article /aside /section footer lorem ipsum /footer 1. Branding 1. Navigation 2. Main Content 1. Welcome 2. Intro 3. Complementary Content 1. Latest News 2. Recent Comments And the following markup and document outline are more appropriate. Since the main is not a sectioning element, now it only serves as an element for keyboard navigation (id=main) and for assistive technology to quick navigate to (role=main). !DOCTYPE html titlelorem ipsum/title header h1Branding/h1 nav h1Navigation/h1 lorem ipsum /nav /header main id=main role=main section h1Welcome/h1 lorem ipsum /section section h1Intro/h1 lorem ipsum /section aside id=comp role=complementary h1Complementary Content/h1 article h1Latest News/h1 lorem ipsum /article article h1Recent Comments/h1 lorem ipsum /article /aside /main footer lorem ipsum /footer 1. Branding 1. Navigation 2. Welcome 3. Intro 4. Complementary Content 1. Latest News 2. Recent Comments If any of my above understanding is flawed, please point it out for me. Thank you all. Sincerely, Ian Yang
Re: [whatwg] Is main now an official HTML5 element?
Sorry, maybe the markup structure still needs some modifications. One thing needs to be figured out is that should aside role=complementary be contained within main role=main? Or rather, is aside role=complementary a supporting content for the entire document or just for main role=main? If it is the latter, then aside is fine being within main. The spec doesn't look like it has clearly defined the relationship between main and aside. Any opinion will be appreciated. Thanks. Kind Regards, Ian Yang
Re: [whatwg] Is main now an official HTML5 element?
Hi Ian, On Thu, 14 Feb 2013 01:31:36 +0100, Aurelio De Rosa aurelioder...@gmail.com wrote: I think this should answer your question: http://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F It doesn't seem to provide much useful information on the differences. According to its charter http://www.whatwg.org/charter, WHAT-WG is a group of 9 individuals who work with a very simple set of rules (basically the editor of a specification decides what should be in it, but the 9 people can decide other things by overwhelming majority). There is a mailing list, IRC, etc, and everyone else who contributes to the discussion is called a contributor. More about how WHAT-WG works is described at http://wiki.whatwg.org/wiki/FAQ The HTML WG is one of the working groups of W3C. The working group has a charter that describes some of how it works: http://www.w3.org/2007/03/HTML-WG-charter W3C itself is a consortium of member organisations, and the links from the HTML WG charter to the process document will lead you into more information about how W3C works. Note that in my personal opinion the Wikipedia page about W3C is outdated and very poor quality information. cheers Chaals Best regards 2013/2/14 Ian Yang i...@invigoreight.com Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner faulkner.st...@gmail.comwrote: Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an open bug on that, which we be dealt with. If you want to discuss the specification of the main element in HTML 5.1 specification feel free mail the html wg list. If you want to discuss definition as per the whatwg spec this is the place, although I will obviously follow ant discussions with interest regards SteveF Date: Wed, 13 Feb 2013 18:31:32 +0800 From: Ian Yang i...@invigoreight.com To: whatwg wha...@whatwg.org Subject: [whatwg] Is main now an official HTML5 element? Message-ID: CABr1FsfcaX8=B8TReG8Sz36W= h1w0hRY61+LG=cebo-zuwy...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi editors and all other folks, I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? However, in spec, it still says that main element is not a sectioning element. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? Sincerely, Ian Yan -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex cha...@yandex-team.ru Find more at http://yandex.com
Re: [whatwg] Is main now an official HTML5 element?
On Thu, Feb 14, 2013 at 12:37 PM, Charles McCathie Nevile cha...@yandex-team.ru wrote: Hi Ian, On Thu, 14 Feb 2013 01:31:36 +0100, Aurelio De Rosa aurelioder...@gmail.com wrote: I think this should answer your question: http://wiki.whatwg.org/wiki/**FAQ#What_is_the_WHATWG.3Fhttp://wiki.whatwg.org/wiki/FAQ#What_is_the_WHATWG.3F It doesn't seem to provide much useful information on the differences. According to its charter http://www.whatwg.org/charter**, WHAT-WG is a group of 9 individuals who work with a very simple set of rules (basically the editor of a specification decides what should be in it, but the 9 people can decide other things by overwhelming majority). There is a mailing list, IRC, etc, and everyone else who contributes to the discussion is called a contributor. More about how WHAT-WG works is described at http://wiki.whatwg.org/wiki/* *FAQ http://wiki.whatwg.org/wiki/FAQ The HTML WG is one of the working groups of W3C. The working group has a charter that describes some of how it works: http://www.w3.org/2007/03/** HTML-WG-charter http://www.w3.org/2007/03/HTML-WG-charter W3C itself is a consortium of member organisations, and the links from the HTML WG charter to the process document will lead you into more information about how W3C works. Note that in my personal opinion the Wikipedia page about W3C is outdated and very poor quality information. cheers Chaals Hi Charles, Thank you for providing resources. I will try to determine what topic belongs to which group in the future. Kind Regards, Ian Best regards 2013/2/14 Ian Yang i...@invigoreight.com Hi Steve, Thanks. And sorry, but til now I still don't understand the differences between whatwg and html wg. Could you please explain? Regards, Ian On Thu, Feb 14, 2013 at 12:59 AM, Steve Faulkner faulkner.st...@gmail.com**wrote: Hi Ian, I cannot speak for whatwg, but from the W3C HTML spec side the main element is in the HTML 5.1 spec and has been implemented in browsers and so will be added to HTML5 spec at some point as it likely meets the CR exit criteria. as for it being a sectioning element, there is currently an open bug on that, which we be dealt with. If you want to discuss the specification of the main element in HTML 5.1 specification feel free mail the html wg list. If you want to discuss definition as per the whatwg spec this is the place, although I will obviously follow ant discussions with interest regards SteveF Date: Wed, 13 Feb 2013 18:31:32 +0800 From: Ian Yang i...@invigoreight.com To: whatwg wha...@whatwg.org Subject: [whatwg] Is main now an official HTML5 element? Message-ID: CABr1FsfcaX8=B8TReG8Sz36W= h1w0hRY61+LG=Cebo-ZUWYfqA@**mail.gmail.comcebo-zuwy...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi editors and all other folks, I saw the SitePoint article Introducing the New HTML5 main Elementhttp://www.sitepoint.**com/html5-main-element/http://www.sitepoint.com/html5-main-element/ yesterday. Does that mean main element has been approved by all editors of the working group? However, in spec, it still says that main element is not a sectioning element. That means, in document outline, main content will form another tree structure instead of appearing under the original website tree structure. Can we have somebody advise on this? Is there a special consideration to not making main a sectioning element? Sincerely, Ian Yan -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex cha...@yandex-team.ru Find more at http://yandex.com
Re: [whatwg] Is main now an official HTML5 element?
I will try to determine what topic belongs to which group in the future. The simple answer is: have your discussion wherever you feel comfortable to have it. Even if the specs differ, in the end what matters is what browsers implement. If a discussion about a topic is more appropriate in a different forum (and that could also be the W3C CSS WG, a W3C Community Group, a IETF list or other list), ppl will soon enough tell you. HTH. Silvia.
Re: [whatwg] Is main now an official HTML5 element?
On Thu, 14 Feb 2013, Ian Yang wrote: In the past, I always regarded a sectioning main content area is an indispensable part in a document. Today, information above tell me that the main content area seem doesn't need to be a titled section. I'm not sure what you mean. main is just there to help you if you need to style the main part of the doc, basically. It's separate from marking up a _section_ of the document, which is what you would do using section or article. So it seems that the following markup contains one unnecessary section and one unnecessary h1, and they cause one unnecessary indent in document outline. !DOCTYPE html titlelorem ipsum/title header h1Branding/h1 nav h1Navigation/h1 lorem ipsum /nav /header section id=main role=main h1Main Content/h1 section h1Welcome/h1 lorem ipsum /section section h1Intro/h1 lorem ipsum /section aside id=comp role=complementary h1Complementary Content/h1 article h1Latest News/h1 lorem ipsum /article article h1Recent Comments/h1 lorem ipsum /article /aside /section footer lorem ipsum /footer 1. Branding 1. Navigation 2. Main Content 1. Welcome 2. Intro 3. Complementary Content 1. Latest News 2. Recent Comments It's easier to discuss with concrete cases. I haven't seen any pages that actually have an explicit main content section title, that seems a bit weird. You don't typically have a section in a book that contains the chapters, separate from the section that contains the table of contents or the appendices. And the following markup and document outline are more appropriate. !DOCTYPE html titlelorem ipsum/title header h1Branding/h1 nav h1Navigation/h1 lorem ipsum /nav /header main id=main role=main section h1Welcome/h1 lorem ipsum /section section h1Intro/h1 lorem ipsum /section aside id=comp role=complementary h1Complementary Content/h1 article h1Latest News/h1 lorem ipsum /article article h1Recent Comments/h1 lorem ipsum /article /aside /main footer lorem ipsum /footer 1. Branding 1. Navigation 2. Welcome 3. Intro 4. Complementary Content 1. Latest News 2. Recent Comments That's fine too (modulo my comments below). You could also just not bother with the main element here, as in: !DOCTYPE html titlelorem ipsum/title header h1Branding/h1 nav h1Navigation/h1 lorem ipsum /nav /header section h1Welcome/h1 lorem ipsum /section section h1Intro/h1 lorem ipsum /section aside h1Complementary Content/h1 article h1Latest News/h1 lorem ipsum /article article h1Recent Comments/h1 lorem ipsum /article /aside footer lorem ipsum /footer 1. Branding 1. Navigation 2. Welcome 3. Intro 4. Complementary Content 1. Latest News 2. Recent Comments It's really an authoring choice. Since the main is not a sectioning element, now it only serves as an element for keyboard navigation (id=main) and for assistive technology to quick navigate to (role=main). It mainly serves as a styling hook. (Accessibility tools can't rely on the page having a main element or an element with role=main, since most pages don't use it. HTML actually provides enough hooks already for UAs to help users navigate a page.) On Thu, 14 Feb 2013, Ian Yang wrote: One thing needs to be figured out is that should aside role=complementary be contained within main role=main? Or rather, is aside role=complementary a supporting content for the entire document or just for main role=main? If it is the latter, then aside is fine being within main. The two elements are orthogonal. You can use one in the other or vice versa, or have them separate, or just one, or have neither. The spec doesn't look like it has clearly defined the relationship between main and aside. There is no relationship. One indicates a section of a page that consists of content that is tangentially related to the content around the aside element, and which could be considered separate from that content, e.g. a sidebar. The other is just a container for the dominant contents of an element. HTH, -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A
Re: [whatwg] Is main now an official HTML5 element?
Hi Hickson, Thanks for the help. There is one thing which makes me confused. You mentioned the main is mainly serves as a styling hook. If what we need is just a styling hook, why was main introduced? We could just use div. So iiuic, the main still has its purpose because it natively has the role main. Please correct me if I'm wrong. Kind Regards, Ian Yang
Re: [whatwg] Is main now an official HTML5 element?
On Thu, 14 Feb 2013, Ian Yang wrote: There is one thing which makes me confused. You mentioned the main is mainly serves as a styling hook. If what we need is just a styling hook, why was main introduced? We could just use div. Yeah, that was my argument too. But browser vendors added it, and the spec matches reality, so I added it to the spec. So iiuic, the main still has its purpose because it natively has the role main. Please correct me if I'm wrong. The main role isn't necessary. IMHO it's a mistake in ARIA that this role even exists. But that's a discussion for the ARIA list; this list is the wrong place to discuss ARIA. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Is main now an official HTML5 element?
Silvia wrote: Even if the specs differ, in the end what matters is what browsers implement. Partially agree, it matters what conformance checkers implement and in the case of main. the major HTML conformance checker will implement the conformance rules in the W3C HTML spec. This will leave the WHATWG spec not matching reality. It should also be noted that as implemented in browsers main is implemented as per the W3C spec i.e. main is mapped to role=main and because of this main is interpreted by AT as a main landmark already. This leaves the WHATWG spec not matching reality. Beyond the priorities and domain of the browser vendors is the conformance requirements and advice the HTML spec provides to authors which can directly impact the experience for users. So I suggest non browser differences matter very much. regards SteveF
