Bug 62605 - shift-delete doesn't put cut into clipboard with text area
Summary: shift-delete doesn't put cut into clipboard with text area
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-04-02 23:31 UTC by James Manning
Modified: 2007-04-18 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-17 13:26:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description James Manning 2002-04-02 23:31:57 UTC
Description of Problem: 
If you highlight a selection of characters in a text area in konqueror 
and hit shift-delete, it no longer puts those characters into the clipboard. 
It *does* put them in the clipboard if it's a input type=text (one-line input) 
but not for textarea.  Easiest to confirm with the comments textarea for a 
bugzilla entry (should be one nearby as you see this :) 
AFAICT, a regression from 2.2.x 
Version-Release number of selected component (if applicable): 
jmm@jmm:/home/jmm> rpm -qf `which konqueror` 
How Reproducible: 
Steps to Reproduce: 
1. go to a page with a textarea 
2. type in some text 
3. select some of it, hit shift-delete 
Actual Results: 
selected text deletes but does not go to the clipboard / cut buffer 
Expected Results: 
should work like the normal input - shift-del should put in clipboard 
Additional Information:

Comment 1 James Manning 2002-05-17 18:09:24 UTC
still a problem in 7.3 - everything works great in mozilla (in a textarea,
whatever you just did a shift-delete on will be what gets pasted when you do a
shift-insert afterwards)

Comment 2 Radek Bíba 2005-02-17 13:26:51 UTC
no problem with kdebase-3.3.1-4.3.FC3, closing...

Note You need to log in before you can comment on or make changes to this bug.