After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745984 - HTML anchors in notifications are not properly formatted.
HTML anchors in notifications are not properly formatted.
Status: RESOLVED DUPLICATE of bug 653033
Product: gnome-shell
Classification: Core
Component: message-tray
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2015-03-10 19:26 UTC by MineyMe
Modified: 2015-03-10 19:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description MineyMe 2015-03-10 19:26:53 UTC
Hello

Whenever a notification is sent that contains an HTML anchor, its body isn't correctly formatted in the notification displayed above the message tray. I didn't think this was intended behavior as other HTML tags (such as b for bold) are correctly parsed. This bug has been present at least since GNOME 3.14, but IIRC was also present in GNOME 3.12.

This can be reproduced by opening a terminal and entering (requires libnotify):
  notify-send --icon=gtk-add "Test" 'This is <b>bold</b>. This is a <a href="http://test.com"><i>link</i></a>'

The bold and italic text markup works just fine, but the HTML anchor is never replaced and ends up unparsed in the final output.

There are a few applications that use these HTML anchors in notifications, such as Mumble and IM clients. The following URL's also relate to the problem:
  - https://github.com/mumble-voip/mumble/issues/1535
  - https://github.com/linuxmint/Cinnamon/issues/2416

My apologies if this is the wrong location for this bug, I wasn't exactly sure where to put it, it is however relevant to the message tray.

Kind regards and thanks in advance
Comment 1 Florian Müllner 2015-03-10 19:32:07 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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