THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened. Details are below. User who did this - Andrei Thorp (garoth)
Attached to Project - awesome
Summary - Libnotify spec requires that we handle some markup
Task Type - Bug Report
Category - naughty
Status - Unconfirmed
Assigned To - Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.4.8
Due in Version - Undecided
Due Date - Undecided
Details - In an uncommon corner of the libnotify spec lurks this page:

http://www.galago-project.org/specs/notification/0.9/x161.html

The basic thing thing to take away is that the libnotify spec *optionally* requires that notify clients (such 
as awesome/naughty) interpret a limited HTML-style markup. Specifically, the <a href=, <b>, 
<u>, <i>, and <img src= tags. If we don't support them, they should be instead filtered out. 
It seems that Awesome supports some of these tags, but not <a>. Probably, what we do is just run the 
text through pango's markup system which doesn't entirely match the libnotify spec.

At the moment, not very many programs seem to use this markup, but you can test that we don't support it by 
using notify-send. Ex: notify-send "<a href=\"blah blah\"> test </a>"

Sorry, don't want to test against next/master while at work, though I think 
this bug probably still exists there.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=876

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to [email protected].

Reply via email to