Re: proposal: subline element

 

	While being able to use  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:: 

	Dr. Strangelove  

	        Or: How I Learned to Stop Worrying and Love the Bomb 

	  

	  

	Starring Peter sellers 
(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" 
To:"Steve Faulkner" 
Cc:"HTMLWG WG" 
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:
 > 
 > 
 > Walking the path of a tornado
 > A journey into the heart of a 17-mile storm
 > 
 > by John D. Sutter, CNNpublished Wed
 > May 29, 2013
 > 

 I think it is a great idea that  could be used both inside and 
 outside heading elements! This would be a definitive advantage
compared 
 with . (And I do think that  needs to be perceived as 
 better than  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