This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24405 - consider to allow multiple <main> for single-page sites
Summary: consider to allow multiple <main> for single-page sites
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2014-01-27 11:51 UTC by Giorgio
Modified: 2014-02-02 22:21 UTC (History)
8 users (show)

See Also:


Attachments

Description Giorgio 2014-01-27 11:51:19 UTC
as summary says, single page sites are frequent these days and they could be an use case for multiple <main> tags
Comment 1 Julian Reschke 2014-01-27 11:59:05 UTC
What is a "single page" site???
Comment 2 Giorgio 2014-01-27 15:05:35 UTC
google "single page sites"

like this one for example www.reverenddanger.com
Comment 3 steve faulkner 2014-01-27 15:23:33 UTC
(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?
Comment 4 Michael[tm] Smith 2014-01-28 11:48:59 UTC
(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.
Comment 5 Michael[tm] Smith 2014-01-28 11:51:01 UTC
(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.
Comment 6 Edward O'Connor 2014-01-31 22:46:03 UTC
See this thread on www-style: http://lists.w3.org/Archives/Public/www-style/2014Jan/0621.html
Comment 7 steve faulkner 2014-02-01 15:25:52 UTC
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.
Comment 8 Michael[tm] Smith 2014-02-02 21:02:40 UTC
(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.
Comment 9 steve faulkner 2014-02-02 22:21:36 UTC
(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.