Hi, No, I mean User Agent
Quote from W3C: "INS and DEL are used to markup sections of the document that have been inserted or deleted with respect to a different version of a document (e.g., in draft legislation where lawmakers need to view the changes). ... User agents should render inserted and deleted text in ways that make the change obvious. For instance, inserted text may appear in a special font, deleted text may not be shown at all or be shown as struck-through or with special markings, etc." On Tue, March 25, 2008 2:13 pm, Svip wrote: > Don't you mean server sided rather than browser/user agent? > > /Svip > > On 25/03/2008, Stuart Foulstone <[EMAIL PROTECTED]> wrote: >> 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-del-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] *******************************************************************
