Closed Bug 72873 Opened 24 years ago Closed 22 years ago

Delete/Backspace key doesn't work until commands updated

Categories

(SeaMonkey :: MailNews: Message Display, defect)

PowerPC
Mac System 8.5
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 122854

People

(Reporter: mikepinkerton, Assigned: mscott)

References

Details

- launch mail - select a message - hit backspace/delete Expected: - mail should be deleted Actual: - nothing happens. - the delete button is active and works as expected. - selecting "Edit" menu shows 'delete message' as enabled, but then appears to do all the necessary command updating. After showing the edit menu, backspace will work. No data loss, just very annoying as users won't quite understand why sometimes keys don't work when the window is first opened.
over to mscott
Assignee: sspitzer → mscott
change qa contact to myself, cc esther
QA Contact: esther → sheelar
i think that the following behavior falls under this bug, but if not, let me know and i'll report it separately: 1] open mail window 2] tab into folder pane 3] use arrow keys to navigate to inbox or some other folder with mail in it. once you are there and pause, focus will automatically go to thread pane. (this exposes a separate bug 78818 if you are too slow using your arrow keys; once bug 78818 is fixed, use tab after getting to desired folder to get to thread pane.) 4] try to delete with key; no action using the delete button & delete key as described below works. also, tab to the message window and delete key seems to work. shift-tab back to msg pane, and delete key continues working. repeat steps 1-4, and delete key will often become inactive again. occurs for me on MacOS9.1 (in addition to reported 8.5), using nightly build 2001060508.
On my setup (IMAP account on Mozilla 0.9.2 build 2001062823 running in Mac OS X Classic mode) the delete key works from within the 3-pane window, but if you open a message, the delete key does not work from the message window--you have to press the delete button in the toolbar or select Edit->Delete Message from the menu. Is this the same problem, or a different problem?
*** Bug 88858 has been marked as a duplicate of this bug. ***
This might be the same as bug 57510
Oops, no, this is not the same as 57510; that bug deals with the del key, not the delete (backspace) key
resembles bug 90539
Keywords: mozilla1.2, nsbeta1
QA Contact: sheelar → stephend
Keywords: mozilla1.2mozilla1.3
Mike/others, I can't reproduce this anymore with the trunk 2003-01-03-08 build on OS X 10.2.3, can you?
I'm lame. Need to try this with an OS 9 build, sorry.
Mail triage team: nsbeta1-
Keywords: nsbeta1-
Keywords: nsbeta1
Mike Pinkerton: if you are still seeing this problem, does your experience match the fairly detailed process in Bug 122854 comment 8? That symptom sounds close to yours, and is still present in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030415 I ask because that bug has been mentioned as a dupe of this one. JohnDoe: The symptom you describe in comment 3 doesn't seem to be reproducible. It sounds like you have turned on the Preference for "Remember the last selected message" -- otherwise, there is no message loaded that I might expect to delete. With this preference set, if I "use tab ... to get to thread pane" (the focus-shifting bug having been fixed), the Delete key deletes the displayed message. James L: the problem you describe in comment 4 appears to duplicate bug 90539, which has been fixed.
This bug is targeted at a Mac classic platform/OS, which is no longer supported by mozilla.org. Please re-target it to another platform/OS if this bug applies there as well or resolve this bug. I will resolve this bug as WONTFIX in four weeks if no action has been taken. To filter this and similar messages out, please filter for "mac_cla_reorg".
*** This bug has been marked as a duplicate of 122854 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Verified dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.