281615 - nsITransactionManager.redoTransaction() throws exception

Status: RESOLVED INVALID

(Core :: DOM: Editor, defect, P5)

Description

[alexander :surkov (:asurkov)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122

I manage transactions in WillInsertText()/DidInsertText() handlers of
nsIEditActionListener interface by beginBatch()/endBatch() methods of
nsITransactionManager interface. When I undo and then redo transaction, I get
exception.

Error: uncaught exception: [Exception... "Component returned failure code:
0xc1f30001 (NS_ERROR_NOT_INITIALIZED) 

[nsITransactionManager.redoTransaction]"  nsresult: "0xc1f30001
(NS_ERROR_NOT_INITIALIZED)"  location: "JS frame :: 

chrome://dc-common/content/bindings/test5.xul :: oncommand :: line 1"  data: no]

When I set src attribute for editor then redoTransaction() works fine.

Reproducible: Always

Comment 1

[alexander :surkov (:asurkov)]

Attachment: testcase

run it with chrome protocol

Comment 2

[alexander :surkov (:asurkov)]

redoTransaction() works fine when changed element has intial text content. In
instance:

<span>hello</span><br/> <!-- there is exception here-->
<span></span> <!-- there is not exception-->

If you will be call redoTransaction() for changes of top span then exception
will not be thrown. If you will be call redoTransaction() for changes of bottom
span then exception will be thrown.

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[alexander :surkov (:asurkov)]

confirm Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050909
SeaMonkey/1.1a

Run testcase, enter test at top editor, press 'undo' and then 'redo' button.

Comment 5

[Serge Gautherie (:sgautherie)]

Can you reproduce with SeaMonkey v2.0.10 or newer?
(or Firefox v3.5.15 or newer?)

Comment 6

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Comment 7

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

It's not called directly in m-c nor c-c except debug addon of SeaMonkey and automated tests.

Please file a new bug if you find redo does not work without modifying the DOM tree with JS.