Closed
Bug 32548
Opened 24 years ago
Closed 24 years ago
Reply at bottom cursor sometimes missing
Categories
(MailNews Core :: Composition, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: jay, Assigned: bugzilla)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; N; Win98; en-US; m14) BuildID: 32011 Prefs | M&N | Messages Reply below quoted text is selected. However, on some messages the reply cursor does not appear anywhere in the composer window and sometimes it does. I noticed that on a short quote that the cursor does appear and on long quotes the cursor does not appear. I have not determined the threshold that produces this anomaly. Reproducible: Always Steps to Reproduce: 1.Configure to reply below quoted text 2.Reply to email or news message 3. Actual Results: Replying to a message with just a few quoted lines the cursor appears at the botton as it should. Replying to a message with a lot of quoted text the cursor does not appear in the body of the reply at all. Expected Results: Expect to see cursor in the correct position on all replies. Have not been able to determine the quote length threshold to produce the no-cursor error.
Comment 1•24 years ago
|
||
This is a compose /editor issue. Re-assigning to ducarroz.
Assignee: mscott → ducarroz
Component: Networking-Mail → Composition
Comment 2•24 years ago
|
||
jay@jaygarcia.com - are you still seeing this problem on recent builds of Mozilla? Gerv
Reporter | ||
Comment 3•24 years ago
|
||
The reply cursor does appear now in the latest builds, however I filed bug #33938 now because although the cursor does appear now, the page doesn't focus where the cursor is, rather the message remains focused at the top of the page rather than moving to the location of the cursor.
Comment 4•24 years ago
|
||
Marking WORKSFORME based on reporter's comments. Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•