Cody, in <https://wiki.ubuntu.com/NotificationDevelopmentGuidelines#escaping> I've included a table of examples that you could use for test cases. (The "As displayed by Notify OSD" column shows what Notify OSD should emit when it implements the design spec, not what it currently emits.;-)
-- Some HTML tags cause all tags to appear as raw code https://bugs.launchpad.net/bugs/339020 You received this bug notification because you are a member of Notify OSD Developers, which is subscribed to Notify OSD. Status in Notify OSD: Confirmed Status in “notify-osd” source package in Ubuntu: Confirmed Bug description: notify-osd 0.9ubuntu2, Ubuntu Jaunty At a terminal, enter: 1. notify-send 'test' '<b>Markup</b> should be <i>filtered</i>.' 2. notify-send 'test' '<b>Markup</b> should be <a href="http://example.com/";>filtered</a>.' What happens: 1. A notification bubble appears with body text 'Markup should be filtered.' 2. A notification bubble appears with body text '<b>Markup</b> should be <a href="http://example.com/";>filtered</a>.' What should happen, as defined in the spec <https://wiki.ubuntu.com/NotifyOSD#Sanitizing%20body%20text>: 1. A notification bubble appears with body text 'Markup should be filtered.' 2. A notification bubble appears with body text 'Markup should be filtered.' In a fallback alert box, the same code apparently causes the body text not to appear at all. <http://launchpadlibrarian.net/23735670/kerneloops-notify-bad.jpg> Fallback alert box text should appear, with exactly the same filtering as notification bubble text has. _______________________________________________ Mailing list: https://launchpad.net/~dx-team Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-team More help : https://help.launchpad.net/ListHelp
