Closed Bug 153145 Opened 22 years ago Closed 16 years ago

can't copy selected text.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jud, Unassigned)

Details

When viewing a mail message (using yesterday's trunk build) and selecting text,
I cannot copy the selected text either via context menu, menu bar->Edit, or ctrl-c.

expected results are that I can copy selected text.
jag, isn't this the thing you were seeing with events being screwed up by the
onscroll stuff?
Jud, can you see if it's fixed in more recent builds?
I hate to say it, but, using the latest Netscape 7.0/1.0 branch build I'm seeing
this in browser windows too (tabbed browser wins to be precise). To get out of
this state, if I minimize all windows, then go back to the selected text, all is
well.
this should probably get re-assigned out of mail. It's clearly a cross
application bug since Jud can reproduce it in the browser. Not sure who owns
that or what component we should assign it to yet.
I guess this isn't the onscroll thing then.
drag and drop copy and middle click copy of selected text are also affected.

Using 2002080421 on Linux Mandrake 8.2
I now see this all the time and with various builds (both Seamonkey and
Firefox). Copy/Cut is fine for the first few minutes afer I open the browser,
but then stops working afterwords. I wonder if it has anything to do with SP2
for WinXP or with another recent non-Mozilla-related installation...

Prog.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Blocks: 96645
Blocks: 133439
No longer blocks: 133439
No longer blocks: 96645
See bugs 133439, 96645, 278927, 153145, 252084, 196897, 101539
The same by me on Firefox 1.5, but registered already on 1.07. WinXP (SP2). Could not cut/copy neither by CTRL+C nor by menu item.
not seeing this anymore.
Judson, what are you running (from help|about)?
=> WFM per reporter
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.