Issue 73923 - "Insert special character" dialog can't be called from dialog edit fields (i.e. "find and replace" dialog)
Summary: "Insert special character" dialog can't be called from dialog edit fields (i....
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: regression
: 71938 74014 (view as issue list)
Depends on:
Blocks: 73858
  Show dependency tree
 
Reported: 2007-01-26 23:17 UTC by trifidus
Modified: 2013-08-07 14:42 UTC (History)
2 users (show)

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

Attachments
Details of Tests (16.65 KB, text/plain)
2007-02-02 04:21 UTC, mirianvincent 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description trifidus 2007-01-26 23:17:13 UTC 
I can't insert special character in "find and change" window using right click,
or ctrl + shift + s
Comment 1 michael.ruess 2007-01-29 09:22:51 UTC 
Reassigned to SBA.
Comment 2 kpalagin 2007-01-29 19:30:02 UTC 
Confirming with build 9110 and 2.1 on WinXP. 
Repro steps:
1. Open Writer, press Crl-F (or click Edit, Find&Replace).
2. R-click in "Search for" field, choose "Special Character" - nothing happens.
Seems to be regression - see http://www.openoffice.org/issues/show_bug.cgi?
id=39293 .

Any chance of targeting for 2.2.1?
Comment 3 kpalagin 2007-01-30 14:09:03 UTC 
*** Issue 74014 has been marked as a duplicate of this issue. ***
Comment 4 kpalagin 2007-01-30 14:10:28 UTC 
Seems that "Special characters" dialog is not invoking in any part of the 
suite.
Increasing priority.
Comment 5 stefan.baltzer 2007-01-30 14:25:08 UTC 
SBA-kapalgin: I was just about to write so, but my changes got lost in that
"mid-air-collision" :-)
Setting P2 may raise the attention, but may well lead to discussions since this
is neither data loss nor a crash. One may discuss if this is a "non-working
central functionality". Or simply "decide", as I did :-)

SBA->PL: As discussed, this worked in OOo 2.04. Broken since OOo 2.1.
I declare this one a showstopper fo r OOo 2.1.
Set target, adjusted summary.
Reassigned to PL
Comment 6 stefan.baltzer 2007-01-30 14:27:20 UTC 
SBA: This is a show stopper for OOo 2.2 (not 2.1, as I mis-typed before.)
SBA: Setting dependency to issue 73858.
Comment 7 philipp.lohmann 2007-01-30 17:49:32 UTC 
svx/source/init/init.cxx became a late victim of warning free code (issue 67487)

fixed in CWS vclshowstop10
Comment 8 kpalagin 2007-01-30 18:31:07 UTC 
sba, pl,
I just love when bug get fixed in less than 24 hours!
Thank you very much!!
Comment 9 mirianvincent 2007-02-02 04:21:18 UTC 
Created attachment 42651 [details]
Details of Tests
Comment 10 mirianvincent 2007-02-02 04:26:24 UTC 
	The above test of Open Office 2.1 (EN version) were done on using the 
Microsoft Windows XP Professional Version 2002 Service Pack 2 Operating system, 
on a Intel ® Pentium® 4 CPU 1.80GHz 1.82Hz, 512 MB of RAM.
Comment 11 philipp.lohmann 2007-02-02 14:59:08 UTC 
please verify in CWS vclshowstop10
Comment 12 owen1234 2007-02-04 18:25:53 UTC 
The same problem is with OOo OOF680_m6
Comment 13 stefan.baltzer 2007-02-05 16:09:16 UTC 
SBA: Verified in CWS vclshowstop10.

SBA->owen1234: Sorry, but you seem to be not aware of the steps that "a fix"
must take to show up on YOUR desktop :-)
The CWS "vclshowstop10" (thus, THE FIX) will probably get integrated in Build
OOF680m7 by the end of this week. 
This is why: 
 - Once a developer has fixed something in the code, it is fixed "on his
machine" only (but already flagged "fixed") - This may irritate some OOo folks
out there....
 - Then the developer will create a CWS (child work space, it looks like an
"entire office", but with one or several bugs being fixed).
 - This CWS must pass the QA, thus certain automated and manual tests must be
passed (The bug really fixed is oONE of them )
 - After QA gave the blessing, it will be "integrated" in the master (into the
code line)
 - Out of this, one can build a new Office, having the fix inside.
 - One more (no, not you, but there WERE others did not know...): to really see
the fix, install that new build on your machine!

=> Thanks for the info, but this one CAN NOT be fixed in OOFm6 yet.
Comment 14 stefan.baltzer 2007-02-14 17:03:11 UTC 
SBA: Verified in OOF m7. Closed.
Comment 15 kpalagin 2007-04-11 08:34:19 UTC 
*** Issue 71938 has been marked as a duplicate of this issue. ***