- From: Andrea Rendine <master.skywalker.88@gmail.com>
- Date: Mon, 26 Sep 2016 12:20:10 +0200
- Cc: "public-html@w3.org LIST" <public-html@w3.org>
- Message-ID: <CAGxST9msOC=H8zSr82ZmJmVmKzkkcJKOcbrNB7kWTOQPeX5LWw@mail.gmail.com>
This leaves the only option to create two new elements from scratch: an inline-list element and an inline-list item element, meant to not close the <p> tag. The only remaining question is, do developers really need it? You state your primary concern is accessibility. But there is a spec dealing with this, WAI-ARIA. You can define your own scheme for inline list using inline elements (namely, span) coupled with role=list for the container, role=group for internal grouping (sublists) and role=listitem for list items. Which is the default do-not-set role for HTML lists. Also note that you can rely upon there attributes to style elements with CSS using attribute selectors. Il 26/Set/2016 12:08, "Steve Faulkner" <faulkner.steve@gmail.com> ha scritto: > > On 25 September 2016 at 23:03, James Cobban <webmaster@jamescobban.net> > wrote: > >> The <ul> and <ol> tags are peers of the <p> and cannot appear within a >> <p>. In HTML a <ul> or <ol> tag *terminates* an unclosed <p> tag as if >> immediately preceded by a </p> >> > > The parsing of the p element in browsers was set in stone many years back > and cannot be changed as it will break too many HTML documents. > > -- > > Regards > > SteveF > Current Standards Work @W3C > <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/> >
Received on Monday, 26 September 2016 10:20:42 UTC