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

Re: Issues of @summary and use of data for "decisions"

From: Simon Pieters <simonp@opera.com>
Date: Wed, 24 Jun 2009 02:30:21 +0200
To: "Shelley Powers" <shelley.just@gmail.com>
Cc: "Steve Axthelm" <steveax@pobox.com>, "Laura Carlson" <laura.lee.carlson@gmail.com>, "Sam Ruby" <rubys@intertwingly.net>, "HTMLWG WG" <public-html@w3.org>
Message-ID: <op.uvz6cvr3idj3kv@simon-pieterss-macbook.local>
On Wed, 24 Jun 2009 02:10:34 +0200, Shelley Powers  
<shelley.just@gmail.com> wrote:

>> It has been argued that summaries would likely be more useful on  
>> avarage if
>> they were visible by default. It has also been argued that some  
>> summaries
>> are useful also to visual users. These are two reasons why HTML5  
>> proposes to
>> put the summary in <caption>, AIUI.
>>
>> --
>> Simon Pieters
>> Opera Software
>>
>
>
> Simon, you've also heard arguments here, from more than one person
> (John, Stephan, Laura) that summaries are more useful not being
> visible.

Yes.


> Can we agree that these people's opinions are just as valuable as
> those who belief otherwise?

Sure.


> But where there is a difference is that if one believes the
> information is useful for everyone, one can use caption. There is
> nothing in having both that precludes putting whatever information is
> deemed useful in caption. This is the most general use.
>
> But collapsing caption into summary is the more restrictive case,
> giving no real option for those who don't want the data to be
> available, except for some CSS trickery. And even that won't work
> today.

Why would the CSS trickery not work today?

-- 
Simon Pieters
Opera Software
Received on Wednesday, 24 June 2009 00:31:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:04 UTC