[Bug 13598] Add guidelines about using ins/del in tables

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13598

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-27 21:32:47 UTC ---
You'd do a whole row or column the same way you'd do a series of items in a
list: just wrap the contents of each cell in that row or column with a <del> or
<ins>.

I would like to study an actual example of a page or document that indicates
the addition or removal of a specific cell (not a row or column). I don't mind
if it's a screenshot of some proprietary software, or an HTML page that does it
today using invalid markup or <font>, or whatnot. But I need to see an example
so that I can understand what it is people are trying to do that needs this.


In the meantime:

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: I've added some text to explain how to mark up adding/removing a row
or column; I haven't added anything about a single cell, due to lacking
sufficient supporting material to explain the use case.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 27 September 2011 21:32:53 UTC