- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Fri, 31 May 2013 07:43:03 +0100
- To: HTMLWG WG <public-html@w3.org>
> Yes, my confusion comes from the fact that, today, H1 accepts only inline > elements, even if the exception in the case of <subline> would be logical. I don't see anything problematic with making the content model for hx Phrasing content + subline but there may well be a whole world of hurt by doing that. the main issue I think is, does adding an element with display:block inside hx break anything? I don't believe so. -- Regards SteveF HTML 5.1 On 30 May 2013 14:29, <contact@thecodeplayground.net> wrote: > > > > ----- Original Message ----- > From: > "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no> > > To: > "Steve Faulkner" <faulkner.steve@gmail.com> > Cc: > "contact" <contact@thecodeplayground.net>, "HTMLWG WG" <public-html@w3.org> > Sent: > Thu, 30 May 2013 15:22:39 +0200 > > Subject: > Re: proposal: subline element > > > Steve Faulkner, Thu, 30 May 2013 14:07:01 +0100: > >>> While being able to use <subline> either as a block or as an inline >>> element seems to be a flexible option, >> >> this is not the intention it is intended to be block either inside or >> outside oh Hx > > Angela touched a relevant issue: the h1-h6 elements currently only take > ’phrasing content’ as children.[1] W.r.t. categories, context and > content model, it seems think <subline> would have to be defined more > or less like <del> and <ins>.[2] > > [1] > http://www.w3.org/html/wg/drafts/html/master/dom.html#phrasing-content-1 > [2] > http://www.w3.org/html/wg/drafts/html/master/edits.html#the-del-element > -- > leif halvard silli
Received on Friday, 31 May 2013 06:44:11 UTC