[Bug 20118] Several clarifications / suggestions for improvement

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20118

--- Comment #5 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to Silvia Pfeiffer from comment #4)
> (In reply to steve faulkner from comment #3)
> > (In reply to Silvia Pfeiffer from comment #2)
> > > (In reply to steve faulkner from comment #1)
> > > >
> > > > > * I think the "Guidance for User Agents and HTML specification editors"
> > > > > section needs to include something about which element should be chosen as
> > > > > the "main" landmark if there are both a <main> element and a role=main and
> > > > > they are different.
> > > 
> > > I don't know where this part of the extension spec ended up.
> 
> I'd still like an answer to this, if you don't mind. :-)

sure, sorry.
I didn't add any guidance yet for a few reasons:
1. there is no reliable way across platforms acc APIs to  differentiate between
<main role=main> and <div role=main>
both are presented in the acc tree as role=main, depending on the acc API the
tagname is available as an object attribute, but its exposure is API dependent.
2. I have been keeping an eye out for use of role=main/<main> in the wild,
grepping data as it becomes available. Happily I have found no use of multiple
<main> or role=main so far , but the number of instances of use is low, so that
may change. I will continue to review data and see what patterns emerge and
base any advice added to the spec on that. 

It may be we end up adding mapping requirements for main like we did for
header/footer, which makes the mapping of banner/contentinfo dependent on
ancestor elements.

"footer element that is not a descendant of an article or section element. -
contentinfo role" 
http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-strong-native-semantics

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 12 May 2014 09:18:07 UTC