Dbus notifications blank if message contains any of: < > &
The notification daemon expects to receive marked up text. Sending it these raw characters < > & causes it to choke on what it sees as invalid markup, and display a notification with a blank body. (XChat also has this issue; they never fixed it.)
A minor annoyance is the notifications always appearing at the location specified in the settings, instead of letting the notification daemon choose where to display it (I have mine set to pop up notifications at top right). It would be nice to have the X and Y position settings optional, and even better, having an option to set the X and Y to wherever the Quassel tray icon happens to be on screen.
The attached patch fixes the blank notifications issue by replacing the offending characters with their HTML entities (< > &) which are correctly decoded and displayed by the notification daemon.
The patch also disables setting the X and Y position hints, disregarding the settings, and letting the daemon decide on position.
The patch is far from optimal. As noted above, there should be options to allow the user to select if the position hints should be sent or not. I don't know anything about the settings system, so I haven't touched it.
Also, Quassel should query the notification daemon about its capabilities, and only send markup if the daemon supports it.
#1 Updated by TerrorBite over 13 years ago
Mantis ate my HTML entities, description should read:
"The attached patch fixes the blank notifications issue by replacing the offending characters with their HTML entities (< > &) which are correctly decoded and displayed by the notification daemon."
#4 Updated by Sputnick about 13 years ago
Thanks TerrorBite, I used some of that information in here, albeit not your patch as I restructured the whole notification thingy :)