Closed Bug 245768 Opened 20 years ago Closed 19 years ago

composer / Mail/News (regression) - insert or update a table of content TOC does not work

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: mmalarm2000-bugzilla, Assigned: mozeditor)

Details

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

insert / toc / insert - no table of content is generated
insert / toc / update - nothing happens
The same problem exists in Mail/News.
Preferences: "Use CSS styles" is deactivated.


Reproducible: Always
Steps to Reproduce:
1. testcase:
<html><head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
<title></title>
<meta content="Markus Merz" name="author">
</head><body>
<h1>1</h1>
jhfliz<br>
<br>
<h1>2</h1>
ug&ouml;o<br>
<h1>3</h1>
lizi&ouml;<br>
<br>
</body>
</html>
2. menu: insert / toc / insert
define h1 as structure for toc, click OK, no table of content is generated
3. same problem in Mail/News

Actual Results:  
In 1.7 it works
since about 10 days it does not work in 1.8a2

Expected Results:  
create or update TOC
Flags: blocking1.8a2?
regression in 1.7rc3
On Monday it worked OK in the latest 1.7 nightly.
For QA 1.7-final I flagged it "1.7?"

1.7rc3:
It's only the presentation while editing, not the sourcecode which fails.

1.8. (June 6th)
Insert TOC doesn't work at all

New in 1.7rc3:
- TOC links are not shown as links anymore. They appear like normal text while
editing. It's only the presentation, not the sourcecode which fails.
- [OT?] If manually creating "h1, body text, h1, body text, h1, body text" the
first body text results in a line shown directly below the h1, all folowing have
a single line added between h1 and body text. It's only the presentation, not
the sourcecode which fails.
Flags: blocking1.7?
Flags: blocking1.7? → blocking1.7-
Flags: blocking1.8a2? → blocking1.8a2-
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/

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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.