Open Bug 265574 Opened 16 years ago Updated 14 years ago

[midas] Undo not working when editing a table programmatically

Categories

(Core :: DOM: Editor, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

UNCONFIRMED

People

(Reporter: nuutti.merilainen, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

  When adding/removing columns/rows programmatically in a table inside an iframe
with designMode="on", undo doesn't work at all.

Reproducible: Always
Steps to Reproduce:
1. Open the provided attachment
2 [review]. Use the buttons to add and delete columns and rows.
3. Push the "Undo" button at any time after adding/deleting rows/columns.

Actual Results:  
  If a table cell is selected, the table's resize handles and inline editing
widgets are repositioned correctly (see bug #265568). No undo actions are
performed, the table is unchanged.

Expected Results:  
  The programmatical modifications should have been undoed.

  Also reproducible on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Gecko/20040910.
  Undo via CTRL-Z shortcut doesn't work either.
You are using standard dom methods, instead of midas specific commands. That's
why undo doesn't work.
It would be nice though if Mozilla also made those methods undoable in a midas
window.
(In reply to comment #3)
> You are using standard dom methods, instead of midas specific commands. That's
> why undo doesn't work.

  I suppose that this bug, then, applies to everything done through the DOM -
not just tables - and that only things done through the execCommand interface
are undo/redoable.
Related/Dupe of Bug 236183?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
Keywords: testcase
QA Contact: bugzilla → editor
Assignee: mozeditor → nobody
You need to log in before you can comment on or make changes to this bug.