Bug 359280

Summary:	Parts of a link get hidden by line break
Product:	[Applications] konversation	Reporter:	Christian Boltz <kde-bugs>
Component:	ircview	Assignee:	argonel <argonel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	justin.zobel, kde, konversation-devel
Priority:	NOR
Version:	1.6
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screenshot - compare the link with the status bar

Description Christian Boltz 2016-02-11 18:46:38 UTC

Created attachment 97154 [details]
screenshot - compare the link with the status bar

I just noticed a bug in displaying a link - if the link gets a linebreak applied, a part of it gets hidden. See the attached screenshot for an example (compare the displayed link with the status bar - hint: the 't' in the last segment isn't displayed).

As a sidenote - I wonder why there is a linebreak at all. The link would easily have fit in the line...

Copying from the chat window gives me the correct link, so this seems to be "only" a display error, but it could still means you'll go to a "wrong" page when clicking the link.

Reproducer:
- paste the following line into a chat window: (without the leading whitespace)
      and again http://www.commitstrip.com/en/2016/02/10/t/ with some text after it
- resize the Konversation window to force a line break in the link

I'm using Konversation 1.6 on openSUSE Tumbleweed (KDE Frameworks 5.18.0, Qt 5.5.1)

Note: I'm not sure if this is a bug in Konversation itsself or in the upper layers (KDE Frameworks or even Qt). Please reassign as needed.

Comment 1 Peter Simonsson 2016-09-09 20:10:47 UTC

*** Bug 363503 has been marked as a duplicate of this bug. ***

Comment 2 Justin Zobel 2020-11-30 03:05:02 UTC

Thanks for the report Christian. I've just tested this but I cannot 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 3 Christian Boltz 2020-11-30 10:01:01 UTC

Testing with the latest Konversation (1.7.7) shows that this bug has indeed been accidently ;-) fixed in the meantime.

Whoever did the fix - thanks!