Closed Bug 92419 Opened 25 years ago Closed 15 years ago

Editing this document messes up HTML

Categories

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

x86
Windows 7
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: neil, Unassigned)

Details

Attachments

(1 file)

Steps to reproduce problem: 1. Edit the attachment 2 [details] [diff] [review]. View HTML Source Actual results: 1. Extra spaces added. Bad when this is next to inline tags. 2. Some <pre> newlines get converted into <br>
Attached file attachment —
I thought we had a 'adds whitespace' bug already, but can't seem to find it, off to jfrancis and cc kin
Assignee: beppe → jfrancis
Priority: -- → P3
Target Milestone: --- → mozilla1.0
fixed
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified in 10-9 Trunk Build
Status: RESOLVED → VERIFIED
I downloaded a nightly after receiving that last Bugzilla message. But the problem still occurs. I would have thought that any fix would have made it in by now :-(
I'm using build 2001100903 and it still isn't fixed.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
removing myself from the cc list
The days of having a half dozen milestones out in front of us to divide bugs between seem to be gone, though I dont know why. Lumping everything together as far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.0.1 → mozilla1.2beta
[ushing these out as far as bugzilla will let me. I'll pull them back as I work on them.
Target Milestone: mozilla1.2beta → mozilla1.4beta
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: REOPENED → NEW
(In reply to neil@parkwaycc.co.uk from comment #0) > 1. Extra spaces added. Bad when this is next to inline tags. Spaces are only added to replace newlines inside tags. This keeps the source code formatting consistent. > 2. Some <pre> newlines get converted into <br> WFM in Seamonkey 2.4.1, no conversion is happening A header <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> and two newlines before </body>. I don't see this a bug anymore.
Severity: major → minor
OS: Windows 95 → Windows 7
Target Milestone: mozilla1.4beta → ---
Works for me as far back as Mozilla 1.6 in fact.
Status: NEW → RESOLVED
Closed: 25 years ago → 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: