W3C home > Mailing lists > Public > public-html@w3.org > June 2013

Re: <subline> becomes <subhead> and other updates

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 21 Jun 2013 15:49:35 +0100
Message-ID: <CA+ri+VkCHAKPsb7VGNnfDRL9YVPOD9fWerbM1MN4GB1GUnK6zg@mail.gmail.com>
To: "Jukka K. Korpela" <jukka.k.korpela@kolumbus.fi>
Cc: HTMLWG WG <public-html@w3.org>
Hi Jukka,

Of course, this would not work, since <small> is mostly something else, and
> much of legalese is not <small>.

do you have data to support this?

what are the main types of use for <small>?

a few I have seen are: is there a common relationship that covers these
apparently disparate uses?

author name +other info

<small>Posted June 17, 2013 By Steph</small>

<small class=nobr" >13&nbsp;Replies</small>

<small class=time">8 min 56 sec</small>


 <small class=muted">(2 days ago)</small>

additional instructions for user input
supplementary text

<small class=small">(include TVA)</small>

<small>*You can include more than 1 category.</small>

<small class=note"><a href="/lost_password.php">Forgot your password

<p class=large center has-tip" title="Manage one website within the account
manager.">Single Site Manager<br /><small>(1 Website)</small></p>

copyright  notices

<small>Copyright 2013 AppAdvice LLC. All rights reserved.</small>

count info:

<small>(10 of <a href=http://www.sickipedia.org/getjokes/today

<small>(30 of 170)</small>


<small><span class=price">Bs.F. 68000</span> </small>

english language translation:

<h2><a href=/activity.php" class="more"



HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 17 June 2013 12:19, Jukka K. Korpela <jukka.k.korpela@kolumbus.fi> wrote:

> 2013-06-17 13:48, Bruce Lawson wrote:
>> If we want to  tighten up the definition of <small> and exclude its use
>> for subheadings, I suggest tightening up the wording:
> The definition of <small> should reflect its actual use, its treatment in
> browsers and other software. This means following the HTML tradition:
> <small> means reduced font size. Anything else means complicated and vague
> definitions - and will hardly change the reality. People will keep using
> <small> if they feel they need it.
>  How about making the definition "The small element represents legalese
>> (often colloquially called "small print") such as disclaimers, caveats,
>> legal restrictions, copyrights,  attribution, or for satisfying licensing
>> requirements."
> That would be an arbitrary definition and would exclude most of the actual
> use that <small> has had, and has. If the definition were taken seriously,
> people (and browsers) could use the CSS rule
> small { display: none }
> in user/browser style sheets, since few people want to see legalese. Of
> course, this would not work, since <small> is mostly something else, and
> much of legalese is not <small>.
>  And make the first note say "It is not appropriate for representing
>> sub-headers or sublines".
>>  Would this imply "...even when the sub-header or subline is legalese"?
> :-)
> From the normative point of you, a note about something not being
> appropriate would not be a conformance requirement, I suppose. But it would
> still be a wrong message: using <small> is the only way of presenting a
> less important part of a heading in a manner that works across all
> browsers, down to the oldest browsers.
> --
> Yucca, http://www.cs.tut.fi/~**jkorpela/ <http://www.cs.tut.fi/~jkorpela/>
Received on Friday, 21 June 2013 14:50:43 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:33 UTC