24405 2014-01-27 11:51:19 +0000 consider to allow multiple <main> for single-page sites 2014-02-02 22:21:36 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED NEEDSINFO a11y P2 enhancement --- 1 giorgio.liscio faulkner.steve eoconnor faulkner.steve john julian.reschke lwatson mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 99151 0 giorgio.liscio 2014-01-27 11:51:19 +0000 as summary says, single page sites are frequent these days and they could be an use case for multiple <main> tags 99152 1 julian.reschke 2014-01-27 11:59:05 +0000 What is a "single page" site??? 99159 2 giorgio.liscio 2014-01-27 15:05:35 +0000 google "single page sites" like this one for example www.reverenddanger.com 99160 3 faulkner.steve 2014-01-27 15:23:33 +0000 (In reply to Giorgio from comment #2) > google "single page sites" > > like this one for example www.reverenddanger.com how would allowing multiple main elements help, with this design, that using article/section would not? 99290 4 mike 2014-01-28 11:48:59 +0000 (In reply to Julian Reschke from comment #1) > What is a "single page" site??? I think it's the same as what's more commonly called a "single page application" or SPA: http://en.wikipedia.org/wiki/Single-page_application ...the kind of Web document/application where, as the user scrolls, more content is dynamically loaded to the DOM and presented to the user. So to some degree in that kind of design, the document can arguably be seen as conceptually a series of logical pages/documents even though it's physically a single page/document. 99291 5 mike 2014-01-28 11:51:01 +0000 (In reply to steve faulkner from comment #3) > (In reply to Giorgio from comment #2) > > google "single page sites" > > > > like this one for example www.reverenddanger.com > > how would allowing multiple main elements help, with this design, that using > article/section would not? Yeah, FWIW, in the case of this particular document at least, it looks to me like it's really more just a series of new sections that are getting loaded as I scroll. 99554 6 eoconnor 2014-01-31 22:46:03 +0000 See this thread on www-style: http://lists.w3.org/Archives/Public/www-style/2014Jan/0621.html 99569 7 faulkner.steve 2014-02-01 15:25:52 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: closed needs info Change Description: no change Rationale: There is no new information or rationale provided, when some does arise please feel free to re-open or file a new bug. 99587 8 mike 2014-02-02 21:02:40 +0000 (In reply to steve faulkner from comment #7) > Status: closed needs info > Change Description: no change > Rationale: There is no new information or rationale provided, when some does > arise please feel free to re-open or file a new bug. (In reply to Edward O'Connor from comment #6) > See this thread on www-style: > http://lists.w3.org/Archives/Public/www-style/2014Jan/0621.html That thread seems like relevant info. At least Ted's reply there does - http://lists.w3.org/Archives/Public/www-style/2014Jan/0634.html Specifically, it seems that in that thread, Leif is describing a case that could possibly be addressed by using <main> multiple times within a single document. So it would be useful to have an answer from the editors about whether or not multiple <main> elements would be useful in the case described in that thread. That said, it's true the OP (Georgio) has not responded yet to the question in comment 3 in this bug, and it'd also be useful to have his answer too. 99589 9 faulkner.steve 2014-02-02 22:21:36 +0000 (In reply to Michael[tm] Smith from comment #8) > (In reply to steve faulkner from comment #7) > > Status: closed needs info > > Change Description: no change > > Rationale: There is no new information or rationale provided, when some does > > arise please feel free to re-open or file a new bug. > > (In reply to Edward O'Connor from comment #6) > > See this thread on www-style: > > http://lists.w3.org/Archives/Public/www-style/2014Jan/0621.html > > That thread seems like relevant info. At least Ted's reply there does - > > http://lists.w3.org/Archives/Public/www-style/2014Jan/0634.html > > Specifically, it seems that in that thread, Leif is describing a case that > could possibly be addressed by using <main> multiple times within a single > document. > > So it would be useful to have an answer from the editors about whether or > not multiple <main> elements would be useful in the case described in that > thread. > > That said, it's true the OP (Georgio) has not responded yet to the question > in comment 3 in this bug, and it'd also be useful to have his answer too. hi mike, I answered ted on list http://lists.w3.org/Archives/Public/www-style/2014Feb/0010.html but to reiterate here, main is not defined in html (W3C at least) as primarily a styling hook, it has a strong, specific and semantic meaning which is conveyed to users. For the use case described in the www-style thread a <div> is appropriate, its an element, essentially without meaning, to decorate visually, whatever bits of content one desires.