Issue 71599 - Cannot paste in search and replace fields
Summary: Cannot paste in search and replace fields
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: Mac Mac OS X, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: eric.bachard
QA Contact: issues@framework
URL:
Keywords: needmoreinfo, oooqa, regression
Depends on:
Blocks: 73922
  Show dependency tree
 
Reported: 2006-11-16 02:30 UTC by cbrunet
Modified: 2011-02-09 11:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description cbrunet 2006-11-16 02:30:08 UTC
When I press CTRL+V in a field of the search and replace box, it writes 'v'
instead of pasting in the content of the pasteboard.

Mac OS X 10.3.9 PPC.
Comment 1 jjmckenzie 2006-11-18 04:35:45 UTC
@eric:
This exists with the Intel build too.  Cannot use Cntrl + v to paste text copied
from a document.
James McKenzie
Comment 2 jjmckenzie 2006-11-18 04:39:42 UTC
Changed to MacIntosh as this affects both Power PC and Intel builds.  Intel
build tested on Mac OS X 10.4.8.  Asking if this happens on other platforms.
James McKenzie
Comment 3 cbrunet 2006-12-02 01:04:14 UTC
I realised that paste doesn't work in any dialog box. For example, try in the
Properties dialog box... It's a regression of 2.0.3.
Comment 4 dridgway 2009-01-07 16:19:52 UTC
This seems to have changed with 3.0. On OOO300m9 OS X 10.5.6 Intel, pasting into
fields works fine for me for both the search and replace dialog and the editable
Properties dialog fields. cbrunet, can you recheck with the latest release?
Comment 5 cbrunet 2009-01-07 16:22:26 UTC
I no longer have a OS X machine to test it... Someone else?
Comment 6 satyam90 2009-02-13 12:21:59 UTC
I have Intel Macbook Pro. I checked in Find & Replace dialog by pasting text in 
both search and replace text boxes. I use "Command+V" to paste. Its working 
fine.
Comment 7 Martin Hollmichel 2011-02-07 12:31:12 UTC
mark as fixed as reported.
Comment 8 Mathias_Bauer 2011-02-09 11:52:52 UTC
closing