RE: Should nesting <header>/<footer> be allowed?

Only the top-level ones will be treated as a landmark for accessibility purposes, so the extra ones shouldn't have any impact on accessible user experience.  I am curious what is the use case for nesting them, however.

From: Travis Leithead [mailto:travis.leithead@microsoft.com]
Sent: Tuesday, May 3, 2016 8:37 AM
To: Chaals McCathie Nevile <chaals@yandex-team.ru>; HTML WG (public-html@w3.org) <public-html@w3.org>
Subject: RE: Should nesting <header>/<footer> be allowed?


No impact on browser implementations-regardless of the outcome. Structurally they are just elements and any element can be nested inside any other element according to the DOM rules.



On the question of semantics and content model validity, that is where the outcome effects other non-browser customers. :)







From: Chaals McCathie Nevile<mailto:chaals@yandex-team.ru>
Sent: Tuesday, May 3, 2016 5:36 AM
To: HTML WG (public-html@w3.org)<mailto:public-html@w3.org>
Subject: Should nesting <header>/<footer> be allowed?


Hi,

Issue 273 https://github.com/w3c/html/issues/273 (and the earlier issue 34
<https://github.com/w3c/html/issues/34> as well) are about <header> and
<footer> elements.

The current specification prohibits nesting them. Is there any obvious
reason to prohibit - or allow - this behaviour? Does it have any practical
impact in implementations, whether browsers, search tools, authoring
systems, etc?

cheers

Chaals

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru<mailto:chaals@yandex-team.ru> - - - Find more at http://yandex.com