- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 30 May 2013 14:07:01 +0100
- To: contact <contact@thecodeplayground.net>
- Cc: HTMLWG WG <public-html@w3.org>
Hi Angela >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 -- Regards SteveF HTML 5.1 On 30 May 2013 13:57, <contact@thecodeplayground.net> wrote: > > > While being able to use <subline> either as a block or as an inline element > seems to be a flexible option, I still think it can be somehow confusing, > especially because there’s no other example (if I’m not wrong) of an HTML > element that behave like that. > > Maybe it would be more precise, from a semantic point of view, to have it as > an inline element, "framed" by a semantic parent block:: > > <h1>Dr. Strangelove > > <subline>Or: How I Learned to Stop Worrying and Love the > Bomb</subline></h1> > > > > > > <p><subline>Starring Peter sellers</subline></p> > > > (I'm new to the mailing list, so sorry if I'm not using the right protocol > :( and this web mail is not helping me much) > > > ----- Original Message ----- > From: > "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no> > > To: > "Steve Faulkner" <faulkner.steve@gmail.com> > Cc: > "HTMLWG WG" <public-html@w3.org> > Sent: > Thu, 30 May 2013 14:25:22 +0200 > Subject: > Re: proposal: subline element > > > > Steve Faulkner, Thu, 30 May 2013 10:15:19 +0100: > >> Thinking more on it this markup pattern would fit: >> >> <header> >> <h1>Walking the path of a tornado >> <subline>A journey into the heart of a 17-mile storm</subline> >> </h1> >> <subline>by <span>John D. Sutter</span>, CNN<br><time>published Wed >> May 29, 2013</time></subline> >> </header> > > I think it is a great idea that <subline> could be used both inside and > outside heading elements! This would be a definitive advantage compared > with <hgroup>. (And I do think that <subline> needs to be perceived as > better than <hgroup> if is supposed to ’win’ the competition.) > >> things that are missing from the spec sketch: >> >> - default UA CSS for subline (aprt from display:block) > > +1 > >> - Related accessibility semantics (as I have suggested in other for, >> the semantics would need a new role/roles added to ARIA (as there are >> no platform API semantics for a subheading etc.), which could then be >> used for default implicit semantics for a native html feature. > > +1 > -- > leif halvard silli
Received on Thursday, 30 May 2013 13:08:15 UTC