Closed Bug 99444 Opened 23 years ago Closed 22 years ago

Won't Save from Composer (comment)

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jones, Assigned: Brade)

Details

Attachments

(1 file)

Mozilla Build ID 2001080110

Steps to reproduce:
1. Open attachment (CPPA2) in Compositor (Mouse Button 2 and Edit)
2. Click HTML button to display HTML text
3. Place cursor as end of line containing "4test4", along with comment start (<!--)
4. Delete with backspace key until line changes
5. In File menu, try to Save As.

Result: File menu half changes, then Compositor doesn't react to KB or mouse.
DrWatson says "nothing unusual". On return to Compositor, window is completely
empty.

Expected Result: File save should have taken place.

This is a simplification. I actually discovered this problem attempting to use
the Browse button in Compositor.
Compositor is for rendering, not the same as the HTML Composer.

->Editor.
Assignee: kmcclusk → kin
Component: Compositor → Editor: Composer
QA Contact: petersen → sujay
Reporter--please attach example file mentioned in steps.
-->Syd
Assignee: kin → syd
Summary: Won't Save from Compositor → Won't Save from Composer
Reporter - you are using a very old build - try and reporduce with a newer
build, downloadable from: http://ftp.mozilla.org/pub/mozilla/nightly/latest/
Responding to: ------- Additional Comments From brade@netscape.com 2001-09-13
07:55 -------
Done.

Responding to: ------- Additional Comments From Cormac F 2001-09-13 08:52
-------Done. I am now using Build 2001091043

Here are some new steps that are easier to "dance":
0. Download attachment
1 [details] [diff] [review]. Start Mozilla Navigator
2. Open attachment in Navigator
3. File/Edit
4. Display HTML text
5. Delete comment follwing the "test" message that had appeared at the end of
the page in Step 2.
6. Attempt to Save As.

Result:
1. Top of browser window is echoed half an inch below.
2. File save menu appears 15 sec later, on a 300 MHz processor with 64M memory;
   File menu appears normal.

Expected result:
File Save menu should appear almost immediately, with no disturbance to File menu.

I said earlier that this report was a simplification. Note that the attached
file contains several "test" comment starts. If I delete them all in Step 5, the
incorrect File menu stays up for at least 15 min. I observed occasional disk
activity, probably but not certainly related to Mozilla. At that point, I
terminated with CTRL-ALT-DEL and End Task.

While doing the above, I also tried clicking on Debug/Start Log while in
Composer and Debug Stop Log after deleting the first test comment and getting to
the File Save menu. But when I search for files modified "today" with Find File,
I did not
find any log files to send you.


Confirming that the several <!-- 's caused my moz to pause for approx 5 seconds
on PII350mhz 128M.  2001092503.  The pause occured every time the page was
rendered (every time I switched from HTML view back to page view.)  However,
despite the slowdown I was still able to edit and save the file.
On an 800Mhz machine I was locked out for about a minute.

Holey moley.
Whiteboard: EDITORBASE
Target Milestone: --- → mozilla0.9.6
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Reassigning to Kathy since she is doing editor save changes. 
Assignee: syd → brade
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.6 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
removing EDITORBASE per meeting
Summary: Won't Save from Composer → Won't Save from Composer (comment)
Whiteboard: EDITORBASE
Status: NEW → ASSIGNED
Keywords: nsbeta1+
is this still a bug?  can someone retest?
Target Milestone: mozilla0.9.9 → mozilla1.0
Peter, please retest this and let us know if its still not working for you...

thanks.
Please update this bug with an [adt1] - [adt3] impact rating (or take it off the
list if it doesn't even rate adt3.)  Thanks!
Keywords: nsbeta1+nsbeta1
Target Milestone: mozilla1.0 → mozilla1.1alpha
Keywords: nsbeta1nsbeta1-
Tested the procedure on the first attachment, deleted from "4test4" to the
"/body" tag, not inclusive. Worked fine with Build 2002031104. I would say the
bug is FIXED.
resolving fixed per bug reporter
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Target Milestone: mozilla1.1alpha → ---
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: