aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000355aMuleMiscpublic2005-04-06 17:202005-04-24 15:34
Reporteragav 
Assigned Token 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product VersionSVN 
Target VersionFixed in Version 
Fixed in Revision
Operating System
Summary0000355: Text in Search Dialog not reformated
DescriptionText in Search Dialog is not reformated after pasting. Copying e.g. a white Text from Safari and pasting it into the search field will result in white formated font in the field.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2005-04-06 17:20agavNew Issue
2005-04-06 17:21agavNote Added: 0000821
2005-04-07 03:06KryNote Added: 0000824
2005-04-07 03:06KryStatusnew => acknowledged
2005-04-07 03:07KryStatusacknowledged => assigned
2005-04-07 03:07KryAssigned To => ken
2005-04-08 01:14XaignarNote Added: 0000836
2005-04-08 01:48kenNote Added: 0000837
2005-04-24 15:34kenStatusassigned => closed
2005-04-24 15:34kenResolutionopen => unable to reproduce

Notes
(0000821)
agav   
2005-04-06 17:21   
Sorry... Forgot that: Mac version!
(0000824)
Kry   
2005-04-07 03:06   
Somehow I suspected a "Mac" after reading "Safari" :P

Assigning to ken, to make his life harder.
(0000836)
Xaignar   
2005-04-08 01:14   
That's strange. The only place where we use a rich-text textctrl is for the chat.
(0000837)
ken   
2005-04-08 01:48   
agav, I was unable to reproduce this. I'm using:

Mac OS X 10.3.8 (Build 7U16)
Safari 1.2.4 (v125.12)
wxMac-cvs as of 2005-04-07 18:49:19 GMT
aMule-cvs as of 2005-04-07 19:26:02 GMT

I copied white-on-black text from http://users.cybercity.dk/~dsl64150/ [^] and pasted into aMule's search field. It appeared black-on-white. I confirmed that the clipboard contained white text by pasting it into TextEdit, where it appeared white-on-white.

Could you provide more specifics about what you were using when you encountered this bug? Please include the version information and the URL, like I provided above.