Bug 352956 - Opening a query by clicking on nick in irc view fails on special characters
Summary: Opening a query by clicking on nick in irc view fails on special characters
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-20 20:33 UTC by Christian (Fuchs)
Modified: 2020-12-02 08:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot showing correct and wrong nick (8.70 KB, image/png)
2017-03-02 13:13 UTC, Oleksandr Natalenko 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2015-09-20 20:33:17 UTC 
Konversation allows to open a query by left-clicking on a nick in the IRC View.
When clicking on a nick with special characters (tested with: |) it converts that character to a html entity (or the likes) and opens a query with the wrong nick

Reproducible: Always

Steps to Reproduce:
1. Open konversation
2. Join a channel with someone with | in the nick  (or open a second connection with a nick containing |)
3. Have the | nick write something
4. click on the nick

Actual Results:  
Query with wrong nick opens

Expected Results:  
Query with correct nick opens
Comment 1 Oleksandr Natalenko 2017-03-02 13:10:19 UTC 
Affects me as well with version 1.6-branch #4910 from Arch Linux.
Comment 2 Oleksandr Natalenko 2017-03-02 13:13:48 UTC 
Created attachment 104315 [details]
Screenshot showing correct and wrong nick
Comment 3 Justin Zobel 2020-11-30 02:47:39 UTC 
I've just tested this and can't replicate the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 Oleksandr Natalenko 2020-12-02 08:00:31 UTC 
The issue has been fixed for quite some time already.