Composer doesn't tidy HTML on save in Normal view

RESOLVED EXPIRED

Status

SeaMonkey
Composer
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Matti, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040729
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040729

The following code

<ul>
<li>
William Shatner ... Captain James Tiberius Kirk</li>
<li>
Leonard Nimoy ... Commander Spock</li>
</ul>

should contract to

<ul>
<li>William Shatner ... Captain James Tiberius Kirk</li>
<li>Leonard Nimoy ... Commander Spock</li>
</ul>

when I save the document with "Reformat HTML source" turned on but it doesn't do
this in Normal view, only if I go to HTML view and delete the carriage return
after the first <li>.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

13 years ago
Assuming you have "Reformat HTML source" radio button checked, when you saved
the document, it does not reformat the HTML source as you indicate but if you
close that document and re-open it, Composer will format and render your
original code like this:

<ul>
   <li>William Shatner ... Captain James Tiberius Kirk</li>
   <li>Leonard Nimoy ... Commander Spock</li>
</ul>

From Help/Help Contents/Contents tab/Creating Web Pages/Composer
Preferences/Composer:
"Reformat HTML source: This option reformats the HTML source code to make it
more readable, by inserting line breaks and indentation."

Tested in Mozilla 1.8a3 build 2004082407 and Nvu 0.4.1 (20040811)
(Reporter)

Comment 2

13 years ago
Yeah, Composer does reformat, but only if I go into HTML View. If I work in
Normal view nothing changes.
Product: Browser → Seamonkey
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
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.