But the whole purpose was to use the semantic value of the <del> to tell
that the listitem was at some point removed. Classes doesn't provide that. I
don't see how grouping comes into this.
From the W3C spec:
"These two elements are unusual for HTML in that they may serve as either
block-level or inline elements (but not both). They may contain one or more
words within a paragraph or contain one or more block-level elements such as
paragraphs, lists and tables."
-Thom
----- Original Message -----
From: "Kyle Hudson" <[EMAIL PROTECTED]>
To: <wsg@webstandardsgroup.org>
Sent: Tuesday, March 25, 2008 5:50 PM
Subject: RE: [WSG] <INS> and <DEL> in lists
Regardless,
Tags are there to markup content, whereas classes are used to group together
tags or markup.
Kyle
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Thomas Thomassen
Sent: 25 March 2008 16:43
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] <INS> and <DEL> in lists
I don't find classes to have the semantic value as the tags have. There is
no where defined what the semanic value of classes are. Even though the
classes would share the same name as a tag I don't see it as having the same
semantic value.
----- Original Message -----
From: "Kyle Hudson" <[EMAIL PROTECTED]>
To: <wsg@webstandardsgroup.org>
Sent: Tuesday, March 25, 2008 3:45 PM
Subject: RE: [WSG] <INS> and <DEL> in lists
Using <del> and <ins> to track changes in a document, is making excellent
use of semantic markup. However markup should only be used to describe
content, not other markup - classes and IDs are used to describe other
markup.
CSS:
del, .del {
display: none;
/* un-comment to use */
/* text-decoration: line-through; */
}
Then on your XHTML
<ul>
<li>Item 1</li>
<li class='del'>Item 2</li>
<li>Item 3</li>
</ul>
Kyle
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stuart Foulstone
Sent: 25 March 2008 13:47
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] <INS> and <DEL> in lists
Hi,
RE:
"When I hid the <del> using display: hidden; the list would render
something like this"
I can't say I've ever felt the need to use these tags, but isn't hiding
the content supposed to be the job of the browser/user agent - rather than
you using CSS.
On Sun, March 23, 2008 12:43 pm, Thomas Thomassen wrote:
I was working on some examples for the use of <del> and <ins>.
http://www.thomthom.net/blog/2008/03/document-history-viewer-making-use-of-d
el-and-ins/
As I was working on this I wanted to mark up a list where items had been
added and removed. That's when I realised that you can't wrap up <li> <dt>
or <dd> in <del> or <ins> elements because <ul>, <ol> and <dl> only allows
list items as their direct child.
The <del> and <ins> then have to be wrapped inside the list item.
<ul>
<li>Item 1</li>
<li><del>Item 2</del></li>
<li>Item 3</li>
</ul>
When I hid the <del> using display: hidden; the list would render
something like this:
* Item 1
*
* Item 3
Because I could wrap up the entire list item, the bullet point would still
remain.
To me it appears illogical to not wrap the <del> or <ins> around the list
items when you add and remove items to the list. I'm guessing it's a case
where every scenario wasn't accounted for when the specifications was
written. (Yes, I know that I could add an extra class to the list item
that I wanted to hide, but it's not the point. It shouldn't be necessary.)
However, when this scenario presents itself I see it as fine to break the
specification and mark it up like this:
<ul>
<li>Item 1</li>
<del><li>Item 2</li></del>
<li>Item 3</li>
</ul>
This seem to render exactly as I expect it to do in every browser I've
tested.
* Item 1
* Item 3
I posted a comment about it in the W3C public HTML discussion group,
hoping it'd be picked up and amend HTML5's specification to allow this.
However, there's yet been any response. Is there any other place I could
air this issue in hope of it getting heards by the authors of the next
HTML specs?
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
