[whatwg] Parsing: comment tokenization

[Anne van Kesteren]

The tokenization section should also handle:

  

as "correct" comments for compat with the web. This means that

  

shows "-->" and that

  

shows "-->".


--
Anne van Kesteren

Re: [whatwg] List captions

[Elliotte Harold]

Andy Mabbett wrote:

How often do we see something like:

Animals:

  Cat
  Dog
  Horse
  Cow


This would be more meaningful as:


  Cat
  Dog
  Horse
  Cow




No, the caption should be displayed to all users. That means it needs to 
be element content, not an attribute value. Just maybe



  Animals
  Cat
  Dog
  Horse
  Cow




but definitely not


  Cat
  Dog
  Horse
  Cow





--
Elliotte Rusty Harold  [EMAIL PROTECTED]
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/

Re: [whatwg] List captions

[Thomas Broyer]

2007/4/6, Andy Mabbett:

>
>We should do our best to avoid repeats of alt, title, and friends.

Why?


Styling, text extraction (a.k.a. tag-stripping)


>A list  header would go much better as a separate element, like
> is for  tables.

Like:

  Animals (or lh, or whatever)
  Cat
  Dog
  Horse
  Cow


Yes, that would work, too.


Problem: not backwards compatible (w.r.t. styling)
See this page with different browsers:
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0A%3Cbody%3E%0A%3Cstyle%20type%3D%22text/css%22%3Eul%20caption%20%7B%20text-decoration%3A%20underline%3B%20%7D%3C/style%3E%0A%3Cul%3E%3Clh%20style%3D%22color%3A%20green%22%3ECaption%3C/lh%3E%3Cli%3EItem%201

You can also try with , almost same results (much better in Firefox).
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0D%0A%3Cbody%3E%0D%0A%3Cstyle%20type%3D%22text/css%22%3Eul%20lh%20%7B%20text-decoration%3A%20underline%3B%20%7D%3C/style%3E%0D%0A%3Cul%3E%3Clh%20style%3D%22color%3A%20green%22%3ECaption%3C/lh%3E%3Cli%3EItem%201

Better results with , but not semantically a good choice.

Using an  or  nested inside a  is not that bad after all...

--
Thomas Broyer

Re: [whatwg] List captions

[Michel Fortin]

Le 2007-04-06 à 10:27, Andy Mabbett a écrit :



  Animals (or lh, or whatever)
  Cat
  Dog
  Horse
  Cow



Personally, I can hardly see why such a markup is needed.

If your list is part of the main content you should be preceding it  
by a header the same way you would for a paragraph. If the list is  
for navigation, why not simply wrap it in a  element alongside  
with a header? If the list is somewhat separate of the main content,  
it probably belongs, with the header, in an  element. If the  
list is for some illustrative purpose, a case were like a table it  
needs a caption, why not improve the  element to allow lists  
to be put inside it?


More visually, which case do you have that would not be covered by  
any of these markups?


Animals

  Cat
  Dog
  Horse
  Cow




  Animals
  
Cat
Dog
Horse
Cow
  




  Animals
  
Cat 
Dog
Horse
Cow
  




  Animals
  
Cat
Dog
Horse
Cow
  




  Animals
  
Cat
Dog
Horse
Cow
  



I believe the markup should depend on what your list stands for. A  
list is not much unlike a paragraph: it's an enumeration formatted in  
a special way. So why can't we reuse the already existing structures?




Michel Fortin
[EMAIL PROTECTED]
http://www.michelf.com/

Re: [whatwg] List captions

[Andy Mabbett]

In message <[EMAIL PROTECTED]>, Magnus
Kristiansen <[EMAIL PROTECTED]> writes

>On Fri, 06 Apr 2007 14:31:58 +0200, Andy Mabbett
><[EMAIL PROTECTED]> wrote:
>
>>
>> How often do we see something like:
>>
>> Animals:
>> 
>>   Cat
>>   Dog
>>   Horse
>>   Cow
>> 
>>
>> This would be more meaningful as:
>>
>> 
>>   Cat
>>   Dog
>>   Horse
>>   Cow
>> 
>>
>> There could also be a summary attribute, as with tables.
>>
>> Any interest?
>
>We should do our best to avoid repeats of alt, title, and friends.

Why?

>A list  header would go much better as a separate element, like
> is for  tables.

Like:

  Animals (or lh, or whatever)
  Cat
  Dog
  Horse
  Cow


Yes, that would work, too.

>The resurrection of  was proposed a few days ago on this very
>list, why not take a look at that thread?

Great minds think alike! ;-)

-- 
Andy Mabbett
*  Say "NO!" to compulsory ID Cards:  
*  Free Our Data:  
*  Are you using Microformats, yet:  ?

Re: [whatwg] List captions

[Kristof Zelechovski]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Mabbett
Sent: Friday, April 06, 2007 2:32 PM
To: WHAT WG
Subject: [whatwg] List captions


How often do we see something like:

Animals:

  Cat
  Dog
  Horse
  Cow


This would be more meaningful as:


  Cat
  Dog
  Horse
  Cow


There could also be a summary attribute, as with tables.

Any interest?

-- 
Andy Mabbett
*  Say "NO!" to compulsory ID Cards:  
*  Free Our Data:  
*  Are you using Microformats, yet:  ?

Re: [whatwg] List captions

[Magnus Kristiansen]

On Fri, 06 Apr 2007 14:31:58 +0200, Andy Mabbett  
<[EMAIL PROTECTED]> wrote:




How often do we see something like:

Animals:

  Cat
  Dog
  Horse
  Cow


This would be more meaningful as:


  Cat
  Dog
  Horse
  Cow


There could also be a summary attribute, as with tables.

Any interest?


We should do our best to avoid repeats of alt, title, and friends. A list  
header would go much better as a separate element, like  is for  
tables. The resurrection of  was proposed a few days ago on this very  
list, why not take a look at that thread?


--
Magnus Kristiansen
"Don't worry; the Universe IS out to get you."

[whatwg] List captions

[Andy Mabbett]

How often do we see something like:

Animals:

  Cat
  Dog
  Horse
  Cow


This would be more meaningful as:


  Cat
  Dog
  Horse
  Cow


There could also be a summary attribute, as with tables.

Any interest?

-- 
Andy Mabbett
*  Say "NO!" to compulsory ID Cards:  
*  Free Our Data:  
*  Are you using Microformats, yet:  ?

Re: [whatwg] Default (informal) Style Sheet

[Anne van Kesteren]

On Fri, 06 Apr 2007 02:22:52 +0200, Sander Tekelenburg <[EMAIL PROTECTED]> 
wrote:

Surely we're not trying to ensure that a Web page
is presented the same in every browsing environment? What would be the
use of that?


That's what people expect from us (browser vendors).


Which people?


Our users expect sites to render correctly. Developers expect browsers to  
render content the same way.




And just because they expect it from you, does that mean you (browser
vendors), let alone 'all of us', should give them that?


Not doing it means less market share. It's a pretty simple equation.



[...]



--
Anne van Kesteren