284443 - Composer doesn't turn on 'changed' bit when Table of Contents is updated

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Gutorm]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

When an existing Table of Content is updated in the composer, the 'document
changed bit' is not set.
So if your document was saved just before you updated the table of contents,
Composer won't let you save your document with the new Table of Contents (even
if the table of contents (and hence the document) was changed.

Reproducible: Always

Steps to Reproduce:
1.Create a document with a table of contents in it.
2.Add and entry that will modify the table of contents
3.save the document
4.Select the Table of Content, and use the menu Insert | Table of Contents | Update


Actual Results:  
The table of contents was updated, but the save button was not enabled.
Of course, people like me that save using ^S get screwed as I think I have saved
my document while it has not been saved.

Expected Results:  
If the document/table of contents has changed, then the Save Button should be
enabled(as well as enablement of the File | Save menu).

I set this as a Normal bug: The workaround is trivial (add and delete a space in
your doc), but I have lost work over and over because of this :-(

Comment 1

[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 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.