Bug 240626 - Hyperlink in notifications not clickable.
Summary: Hyperlink in notifications not clickable.
Status: RESOLVED DUPLICATE of bug 238108
Alias: None
Product: plasma4
Classification: Unmaintained
Component: notifications (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 18:31 UTC by John Brodie
Modified: 2010-06-03 22:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Brodie 2010-06-03 18:31:06 UTC
Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

Using notify-send, notifications which include hyperlinks do not launch the web browser.  Have tried with the default browser set to both Konquerer and SwiftFox.  The cursor also does not reliably switch to the "hand" cursor, although the link does appear properly (blue text, underlined, with the right text). 

This is reproducible every time using libnotify-bin version: 0.4.5-1 on Debian Squeeze.  If any additional information is needed, please let me know and I'll do my best to provide it.


Reproducible: Always

Steps to Reproduce:
notify-send test "<a href=http://www.example.com>this should be clickable</a>" (with libnotify1 and libnotify-bin (and all dependencies) installed).

Actual Results:  
A hyperlink appears, which seems to be properly formed, but is not clickable, with cursor change not always happening on hover.

Expected Results:  
Should reliably change cursor and, on click, launch browser.
Comment 1 John Brodie 2010-06-03 18:34:04 UTC
Forum post with developer stating the same behavior for him: http://forum.kde.org/viewtopic.php?f=64&t=88226&p=160169#p160150
Comment 2 Kevin Krammer 2010-06-03 19:00:55 UTC
I can confirm this on 4.4.4, Debian Unstable.

The mouse cursor actually changes to hand when moved over the link for the second time.
Comment 3 Marco Martin 2010-06-03 22:45:00 UTC

*** This bug has been marked as a duplicate of bug 238108 ***